Valery_Kondakoff

(For me) one of the most annoying things in a daily Max patching is accidentally pressing Enter when creating message while trying to finalise it. This happens dozen times a day! Instead of finalising my message Enter inserts a new line, which disappears after I click outside the newly created message, or press Shift-Enter.

Anyone else is suffering of this? At least I saw this issue many times in Max video tutorials in Youtube/Vimeo.

Why there is a new line in the message if Max does not supports new lines in messages? Is it possible to change the logic of finalising the message and let Enter finalise it? Please! Or there are some drawbacks in implementing this?

message.mov

Max Greatest Annoyances #2: Max tabbed window grows in size every time you open/close the sidebar

Max Greatest Annoyances #3: new objects are created right on top of the others

Max Greatest Annoyances #4: newly created attrui objects size is too small

Max Greatest Annoyances #5: it is possible to save a patch using one of the ‘reserved’ names

Max Greatest Annoyances #6: difficult to transform (change, re-instantiate) graphical Max objects

Max Greatest Annoyances #7: the documentation is fragmented, full of typos and somewhat outdated

Max Greatest Annoyances #8: outdated JavaScript version used in js and jsui object

Anyone else is suffering of this? At least I saw this issue many times in Max video tutorials in Youtube/Vimeo.

Why there is a new line in the message if Max does not supports new lines in messages? Is it possible to change the logic of finalising the message and let Enter finalise it? Please! Or there are some drawbacks in implementing this?

Max Greatest Annoyances #2: Max tabbed window grows in size every time you open/close the sidebar
Max Greatest Annoyances #3: new objects are created right on top of the others 
Max Greatest Annoyances #4: newly created attrui objects size is too small 
Max Greatest Annoyances #5: it is possible to save a patch using one of the ‘reserved’ names 
Max Greatest Annoyances #6: difficult to transform (change, re-instantiate) graphical Max objects 
Max Greatest Annoyances #7: the documentation is fragmented, full of typos and somewhat outdated 
Max Greatest Annoyances #8: outdated JavaScript version used in js and jsui object


Hello!
(For me) one of the most annoying things in a daily Max patching is accidentally pressing Enter when creating message while trying to

feature-request-press-enter-to-finalise-message-when-creating

this happens to me too; Mister 74 should fix it, because it's inconsistent with use of enter key with other objects

yet it is the expected behavior for a text engine

I don't complain for the same behaviour in comment object, because you can create multiline comments. But as the multiline messages are not supported (except for the semicolon syntax, which is another story), I still think pressing Enter should finalise message, just because Enter has no other functionality in this object.

then again, shouldnt enter not also trigger output in that case? :)

No I don't think the Enter should trigger output. 

 you create the message box, enter some text and when you press Enter just nothing happens: the new line appears, which disappears again if you enter Shift-Enter or click outside of message box to finalise the object.

you create the message box, enter some text and press Enter to finalise the object. No output is triggered, as we are in Edit mode.

No I don't think the Enter should trigger output. 

Here is the current behaviour: you create the message box, enter some text and when you press Enter just nothing happens: the new line appears, which disappears again if you enter Shift-Enter or click outside of message box to finalise the object.
Proposed behaviour: you create the message box, enter some text and press Enter to finalise the object. No output is triggered, as we are in Edit mode.

A message box is more similar to an object box than to a text editor box, multi-line text is not even used in it, so the current implementation makes no sense whatsoever.

Agreed, Valery Kondakoff.
A message box is more similar to an object box than to a text editor box, multi-line text is not even used in it, so the current implementation makes no sense whatsoever.

i was about to say "but thats how his sisters, the numberboxes work, for example."

hmmmm i'm not sure, it's consistent with every other text editing objects in Max, it can help reading when you type in a long message at time of creation ; even if it doesnt create an actual inline it does separate symbols (so it's like a press of the spacebar) and i got used to shift enter, for message box and comment and object box alltogether. Not sure how it would piss me off if i just needed to enter for a message box, BUT the same in a comment box would just create an inline... Maybe leaving new lines in message box would be better ?

I'm pretty sure the ability to finalise message object by pressing Enter should be made optional (a checkbox in Max settings).

@Vichug: you make a good point at the end of your post. I too would like to have control over the line breaks of message boxes, particularly when I use them to send multiple messages separated by commas as in:

Visually it would be more intuitive than having a single line with all the commands...

@Vichug: you make a good point at the end of your post. I too would like to have control over the line breaks of message boxes, particularly when I use them to send multiple messages separated by commas as in:
reset,
do_x,
do_y,
bang
Visually it would be more intuitive than having a single line with all the commands...

Do you know that you can press the tab key to finish the creation of the object?

Sorry to bump an old post, but this is the number one inconsistency in max that's been bothering me for years and I just couldn't pass on the opportunity to address it.

Currently, there are three ways to finalize an object that I know of: 

    •    Pressing shift+enter  

but each of those are very situational. Pressing enter will finalize any object apart from the message object and the comment object. Pressing shift+enter will finalize any object. Pressing tab will finalize and remove mouse focus from any object, unless the autocomplete menu is open - if that's the case, it won't do anything.

Ok, if the inconsistencies are bothering me so much, why not start using the consistent shift+enter to finalize any object and stop complaining? This is indeed what I've been doing for many years, but the introduction of 

 changed all that. Patching mechanics introduced some really useful features, for example pressing shift+N to create a new connected object. Unfortunately, the keyboard shortcuts introduced here resulted in yet another layer of inconsistencies, since shift+enter now duplicates the behaviour of shift+N for unfinished object boxes, so what happens now?

Pressing enter: if not message/comment: finalize, else new line. 

Pressing shift+enter: if message/comment: finalize, if finalized object: edit, else create new connected object. 

Pressing tab: if autocomplete menu open: do nothing, else finalize and deselect (so that patching mechanics cannot be used). 

Pressing shift+N: if not finalized: insert "N", else create new connected object.

If there was a consistent way to finalize an object (without deselecting it), you would know that no matter what type of object you have selected (and no matter if you're in editing mode or if it's finalized), you can always press that shortcut followed by shift+N to create a new object connected to the current, instead of juggling a number of hotkeys depending on state and type of object.

Sorry to bump an old post, but this is the number one inconsistency in max that's been bothering me for years and I just couldn't pass on the opportunity to address it. 

Currently, there are three ways to finalize an object that I know of: 
	•	Pressing enter  
	•	Pressing shift+enter  
	•	Pressing tab  
but each of those are very situational. Pressing enter will finalize any object apart from the message object and the comment object. Pressing shift+enter will finalize any object. Pressing tab will finalize and remove mouse focus from any object, unless the autocomplete menu is open - if that's the case, it won't do anything. 

Ok, if the inconsistencies are bothering me so much, why not start using the consistent shift+enter to finalize any object and stop complaining? This is indeed what I've been doing for many years, but the introduction of Patching Mechanics changed all that. Patching mechanics introduced some really useful features, for example pressing shift+N to create a new connected object. Unfortunately, the keyboard shortcuts introduced here resulted in yet another layer of inconsistencies, since shift+enter now duplicates the behaviour of shift+N for unfinished object boxes, so what happens now? 

Pressing enter: if not message/comment: finalize, else new line. 
Pressing shift+enter: if message/comment: finalize, if finalized object: edit, else create new connected object. 
Pressing tab: if autocomplete menu open: do nothing, else finalize and deselect (so that patching mechanics cannot be used). 
Pressing shift+N: if not finalized: insert "N", else create new connected object. 

the most frequently used method to finalize an object is... to click elsewhere. it is the only method you should need.

and if you ask me, all of these keyboard commands should be optional, too.


the most frequently used method to finalize an object is... to click elsewhere. it is the only method you should need.

and if you ask me, all of these keyboard commands should be optional, too.



Max Greatest Annoyances #1: messages are not finalised by pressing Enter