[BUG] not all flags messages works with number and flonum
There is a bug with the most of the flags messages to number and flonum.
Only the "flags 32" bit works, the others doesn’t.
This is with Max 5.0.2 on MacOS 10.4.11 and a MacBook Pro 2.2 GHz
----------begin_max5_patcher---------- 534.3ocwV1rabBCDG+L7TXwkdIKxX9XgppJ0i8YnJpxK3v5DvdE1nrsQ4cul wPCIk.jt6lbwVd7XOC+772lGbc71IOxTdnOi9Axw4AWGGvTmAm9wNd0zi4UT E3lWtrtlIzdWYmSyNpA6eYCJuhmeGZyWGlSzVyEULMrvfdi2HEZE+2LvFwG+ juxV8fyCV4EvdK2c6lfrgs8.UmumKJ+YCKWaS8f3XyNY5B551BsDrOFc8nnJ n0PT89VCmVg9tlZxWut4ez0sq4pSDA6ZKQ2y06Q2TQKUHt.Y9p1wZPTQgwlz LZXMUbAKW1JfERVMuRWfWGZXJSlQ0boXLdvQcDIDfDtu4urYLjSlAxYvJiy. RmF10Ek99yXMRumqPERlR7Isuu+4qb6UvGgXqtxRVjegyvOBwhNBftrrKaQp sz6zYCYUrgjjNIaraj9WGXV283cmoliQpnzaRBFsBBlAwLFuBB9+ftZlRQKY +SsmUVGgyRlDqj2BVCVBqfhsmtKi0oYY7rrL0dkYWFhRRrp5yNKeMcLnguW1 bm5x7ZAYtKxhFoCSheO0gZytIJqXiS6Kl1Lj.mpj.74QatcYl9gpLCIWbcYH 19TPPvInKm8Q1vQpx3v2npDbC94hW7OcPj5r+b3pjsM4C45vUFnmhVASo4B. BicJ5YNsmWTvDiqnq4EGjlpo9j.c8jG0qMmRVQJs8DxHyfGc+CPxeYYm -----------end_max5_patcher-----------
While at it I would suggest a new option/attribute "Don’t send value on
deselect". This could be usefull when typing new values into numer boxes
with the keyboard, which I tend to do a lot. Also in live situations…
I would recommend using the attributes found in number’s inspector for these kinds of things now.
OK, but shouldn’t it work, its in the reference?
But then again, if there is there another way of changing the appearence
of number boxes on the fly, fx. between displaying integer values and
midi note names…
The flags message is provided for legacy support. These things can now be set via object attributes.
Our documentation has been updated for the next update.
On 6 juin 08, at 19:28, Jakob Riis wrote:
> OK, but shouldn’t it work, its in the reference?
> But then again, if there is there another way of changing the
> of number boxes on the fly, fx. between displaying integer values and
> midi note names…
You can with the format attribute. In the next incremental the flags
message will work as it was in 4.x, although as Ben said, using the
attributes is the way to go now.
>You can with the format attribute.
Aaahh thanks a lot!
I missed that one – need new glasses :-)
On 6 juin 08, at 21:14, Jakob Riis wrote:
>> You can with the format attribute.
> Aaahh thanks a lot!
> I missed that one – need new glasses :-)
You can figure out the name of the attributes easily in the inspector
if you click in the "Show Attributes Names" button in the inspector’s
toolbar, or you can drag the attribute from the inspector to the patch/
object to create a message box automatically with the name of the