Forums > MaxMSP

deactivating flonum

October 4, 2006 | 3:00 pm

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



jln
October 4, 2006 | 4:50 pm


October 4, 2006 | 6:15 pm

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
> changing values….

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

max v2;
#N vpatcher 10 59 639 437;
#P window setfont "Sans Serif" 9.;
#P window linecount 4;
#P comment 347 249 204 196617 You can choose two flag states and just
bang these messages to flonum through universal if you don’t want the
whole checklist in your patch.;
#P window linecount 1;
#P message 402 220 149 196617 flags 32;
#P newex 402 152 62 196617 prepend set;
#P flonum 51 56 35 9 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 90 56 35 9 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 470 152 78 196617 prepend flonum;
#P newex 470 177 52 196617 universal;
#P window setfont "Sans Serif" 10.;
#P comment 70 154 143 196618 Transparent;
#P comment 70 138 143 196618 Can’t Change;
#P comment 70 122 143 196618 Output Only on Mouse-Up;
#P comment 70 90 143 196618 Bold;
#P comment 70 106 143 196618 Draw Triangle;
#P window setfont "Sans Serif" 9.;
#N vpatcher 578 423 978 723;
#P window setfont "Sans Serif" 9.;
#N vpatcher 31 70 431 370;
#P window setfont "Sans Serif" 9.;
#P newex 104 177 38 196617 +;
#P newex 132 143 27 196617 * 2;
#P newex 104 118 38 196617 unpack;
#P outlet 104 217 15 0;
#P inlet 104 60 15 0;
#P connect 0 0 2 0;
#P connect 2 0 4 0;
#P connect 4 0 1 0;
#P connect 2 1 3 0;
#P connect 3 0 4 1;
#P pop;
#P newobj 191 67 55 196617 p minmax?;
#P newex 86 116 27 196617 t b i;
#P newex 34 140 79 196617 +;
#P inlet 191 36 15 0;
#P message 191 214 35 196617 $1 $2;
#P outlet 191 238 15 0;
#P message 34 165 45 196617 flags $1;
#N vpatcher 398 320 919 680;
#P window setfont "Sans Serif" 9.;
#P newex 26 261 27 196617 +;
#P newex 172 134 42 196617 * 8192;
#P newex 26 225 27 196617 +;
#P newex 26 194 27 196617 +;
#P newex 96 194 27 196617 +;
#P newex 131 134 35 196617 * 128;
#P newex 96 134 30 196617 * 64;
#P newex 61 165 30 196617 * 32;
#P newex 61 134 29 196617 == 0;
#P newex 26 134 27 196617 * 4;
#P newex 26 99 153 196617 unpack 0 0 0 0 0;
#P outlet 26 301 15 0;
#P inlet 26 46 15 0;
#P connect 0 0 2 0;
#P connect 2 0 3 0;
#P connect 3 0 9 0;
#P connect 9 0 10 0;
#P connect 10 0 12 0;
#P connect 12 0 1 0;
#P connect 5 0 9 1;
#P connect 8 0 10 1;
#P fasten 11 0 12 1 177 246 48 246;
#P connect 2 1 4 0;
#P connect 4 0 5 0;
#P connect 2 2 6 0;
#P connect 6 0 8 0;
#P connect 7 0 8 1;
#P connect 2 3 7 0;
#P connect 2 4 11 0;
#P pop;
#P newobj 34 67 75 196617 p checkstoflags;
#P newex 272 67 55 196617 route flags;
#P message 34 214 80 196617 $3 $4 $5 $6 $7;
#P outlet 272 238 15 0;
#P inlet 272 36 15 0;
#P outlet 34 238 15 0;
#P inlet 34 36 15 0;
#P connect 0 0 6 0;
#P connect 6 0 11 0;
#P connect 12 0 11 0;
#P connect 11 0 7 0;
#P connect 5 0 4 0;
#P connect 4 0 1 0;
#P connect 13 0 12 0;
#P connect 12 1 11 1;
#P connect 10 0 13 0;
#P connect 5 0 9 0;
#P connect 9 0 8 0;
#P connect 2 0 5 0;
#P connect 7 0 3 0;
#P connect 5 1 3 0;
#P pop;
#P newobj 350 110 130 196617 p flags;
#P user radiogroup 51 88 165 80;
#X size 5;
#X offset 16;
#X inactive 0;
#X itemtype 1;
#X flagmode 0;
#X set 0 0 0 0 0;
#X done;
#P flonum 128 56 35 9 0 0 32 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P comment 54 178 204 196617 This was taken out of the flonum
inspector.;
#P fasten 3 0 2 0 355 133 323 133 280 85 56 85;
#P fasten 2 0 3 0 56 171 278 171 321 101 355 101;
#P fasten 3 2 13 0 475 139 407 139;
#P connect 13 0 14 0;
#P connect 3 2 10 0;
#P connect 10 0 9 0;
#P pop;

Vlad Spears
Urbi et orbi

http://www.2secondfuse.com



jml
October 4, 2006 | 7:12 pm

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

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

jl



jln
October 4, 2006 | 8:27 pm


October 4, 2006 | 8:35 pm


October 4, 2006 | 9:00 pm

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.

http://arts.lu/roby/

Roby



jln
October 4, 2006 | 9:01 pm


October 4, 2006 | 9:28 pm

On Oct 4, 2006, at 2:02 PM, jln wrote:

> 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."

Vlad


October 4, 2006 | 9:39 pm

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



jln
October 4, 2006 | 10:50 pm


Viewing 11 posts - 1 through 11 (of 11 total)