redhexagonal

is there a way to deactivate flonum other than clicking outside it?

ideally to deactivate any/all flonums.. i keep accidentally changing values....

is there a way to deactivate flonum other than clicking outside it?
ideally to deactivate any/all flonums.. i keep accidentally changing values....


deactivating-flonum

On Oct 4, 2006, at 8:00 AM, bin ray wrote:

> is there a way to deactivate flonum other than clicking outside it?

> ideally to deactivate any/all flonums.. i keep accidentally 

Here's the basic state changer I pulled from the inspector and piped 

>
> is there a way to deactivate flonum other than clicking outside it?
> ideally to deactivate any/all flonums.. i keep accidentally  
> changing values....

Here's the basic state changer I pulled from the inspector and piped  
to all [flonum] through [universal]:

Vlad Spears
Urbi et orbi
http://www.2secondfuse.com

yeah, this has been discussed a couple times on the list...

create a new object via scripting and immediately delete it.

one possible workaround:
create a new object via scripting and immediately delete it.
not very elegant... but it works.

If you're on Mac you might take a look at rs.floatbox and rs.numbox.

They never have keyboard focus, one of the reasons I coded them.

On 4 oct. 06, at 17:00, bin ray wrote:
> is there a way to deactivate flonum other than clicking outside it?
> ideally to deactivate any/all flonums.. i keep accidentally  
> changing values....

If you're on Mac you might take a look at rs.floatbox and rs.numbox.
They never have keyboard focus, one of the reasons I coded them.

> Yes you're right indeed. But, unless I am missing something, only 

> one numbox can be selected at once ? The js example is quite nice 

> since you can connect all flonum and they'll be deselected or send 

> a bang to the js to deselect any object. I'm not sure I get the 

> example you posted actually. It doesn't deselect numbox, does it ? 

> Maybe I did not understand correctly the initial question actually...

Oh yeah, I love the js example you linked. I've been keeping a copy 

in my frequent use collection for some time.

What I posted will let Bin toggle whether any changes can be made to 

any [flonum] in the patcher. If you tick "Can't Change," all the 

[flonum] in the patcher will be locked from mouse-changing or from 

accidentally kept keyboard focus, but can still display any numbers 

coming into them. It was the only thing that made sense to me when 

Bin said "de-activate all flonums at once."

> Yes you're right indeed. But, unless I am missing something, only  
> one numbox can be selected at once ? The js example is quite nice  
> since you can connect all flonum and they'll be deselected or send  
> a bang to the js to deselect any object. I'm not sure I get the  
> example you posted actually. It doesn't deselect numbox, does it ?  
> Maybe I did not understand correctly the initial question actually...

Oh yeah, I love the js example you linked.  I've been keeping a copy  
in my frequent use collection for some time.

What I posted will let Bin toggle whether any changes can be made to  
any [flonum] in the patcher.  If you tick "Can't Change," all the  
[flonum] in the patcher will be locked from mouse-changing or from  
accidentally kept keyboard focus, but can still display any numbers  
coming into them.  It was the only thing that made sense to me when  
Bin said "de-activate all flonums at once."

thanks. the deselect.js thng will fix it good. sorry for not searching. that is a useful script

actually i meant just deselect the last thing clicked, wasnt thinking straight. that universal patch is pretty cool too, never used that object

deactivating flonum