if this is evaluated from the listener or is in a script
(normalize (random [-1.0,-1.0,-1.0] [1.0,1.0,1.0])
the parser fails to notice the syntax error and the script needs to be interrupted with the escape key ?
it is expecting you to finish the expression on the next line. if you type ) and press enter your expression will execute.
oh i see, it thinks it’s sees a code block separator not “precedent” brackets thats why most other languages use a separate tokens for code blocks. Though when in a script you would think it would report some kind of error (as there is a token mismatch) instead of just sitting there doing nothing :surprised
this behavior of mxs execution in listener was designed in purpose. max has two listeners. the second is one-line. so only this behavior allows user to type multi-line code. long long ago the user had only one and small screen display… you get what i mean, do you?
for the same reason mxs supports “;” code separation.
thats funny because I’ve got max versions going back to 1.2 in the office and I can’t ever remember needing to work like that
because it was designed it doesn’t automatically mean it was used.
btw i’ve never worked with the one-line listener. the main reason why was not is that the listener is placed on left side of the editor. that was very bad solution. not only me but many users feel uncomfortable with that.
for example one-line editor in maya i use all the time.