Forums > MaxMSP

hint and forbidden symbol


jln
October 31, 2006 | 4:14 pm

Hi,

I juste noticed a (personally) unknown behavior from [hint]. If you
try to set ‘list blabla’, [hint] will only display ‘blabla’. The same
happens if your message start with ‘int’, ‘float’ or ‘bang’. ‘List’,
‘Float’, ‘Int’ or ‘Bang’ work however. Is it a feature to force users
not to start a sentence with a lowercase letter so that the comments
are grammatically corrects, or is this a bug ?…

Anyway, it’s probably not a big problem, but I just thought I’d post
it since I haven’t found any post about it.

This behavior happens with Max 4.5.7 and 4.6.2 under OSX.

Best,

Julien.


October 31, 2006 | 5:54 pm



jln
October 31, 2006 | 6:15 pm


October 31, 2006 | 6:29 pm

Have you also noticed how commas get magically erased in the hint text? To separate phrases I wind up using … instead. the same thing happens in drop-down menus, even when using the backslash to escape the comma: it works once, then if you do a Get Info… again, they get erased.

I imagine this is unavoidable, and is really not a big deal, just a quirk.

–CJ


November 1, 2006 | 7:56 am

The problem here is still the use of reserved symbols which get sent as messages from the inspector, and hence end up losing the reserved word where it comes first in the textbox. You can enter phrases like this by using double quotes around your text in the inspector (eg. "list blah blah", but you’ll have the same problem CJ mentioned about commas where the next time you open the inspector the word will disappear and your hint will be incorrect. Probably easier just to avoid this problem in the first place. It’s only a few words……..

Alex


November 5, 2006 | 4:39 pm

jln wrote:
> I juste noticed a (personally) unknown behavior from [hint].

not hint specific

> If you try to set ‘list blabla’, [hint] will only display ‘blabla’.
> The same happens if your message start with ‘int’, ‘float’ or ‘bang’.

These are all reserved words/messages…

> ‘List’, ‘Float’, ‘Int’ or ‘Bang’ work however.

Obviously case sensitive…

> Is it a feature to force users not to start a sentence with a
> lowercase letter so that the comments are grammatically corrects, or
> is this a bug ?…

try to answer it yourself by typing other lowercase messages like "bug"
"hey is this a bug?" or any other words exept reserved words…

> This behavior happens with Max 4.5.7 and 4.6.2 under OSX.

This even happens with older (done to 1.0, though I am not sure if hint
existed that time) and will likely happen with newer versions of Max as
well…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


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