Mike S

i've been getting in to the UI side of max lately and i've found one annoying little characteristic.

for example i have a space where i will have controls for an effect, depending on the effect chosen i will add/remove the relevant controls to the presentation. but when i remove an item from the presentation it forgets where it was placed when it is added again. this isn't really a big deal, you can just send it a message 'presentation_rect 123 123 123 123' to get it back to the right spot, but is there any chance of the object remembering where its original presentation position was?

feature-request-object-remembers-previous-presentation-position

You can still use the "hidden" message in presentation mode just to hide objects. You might also want to look at using the "offset" message to [bpatcher] to change UI views as demonstrated in the helpfile.

i had a sneaky feeling there might have been an obvious solution. the hidden message is what i need

actually, after working with the hidden message, i have concluded it is actually a pain to arrange things like this. the main reason being when you unlock the patch in presentation to move things around, you see everything that is hidden, which is basically a big jumble of text and boxes.

If you have several different UI setups you want to select from look at using something like [tab] and [bpatcher] as shown in the subpatch in the latter's helpfile. No more problems with objects on top of each other, you can create your individual layouts and then change the "offset" to display whichever one you want.

is kind of my point, why do i want to write that for each UI element?

thanks luke, i have looked at bpatcher before, i kind of prefer to have everything in one patch though. i wonder how hard my original request would be to implement?

is kind of my point, why do i want to write that for each UI element? 

thanks luke, i have looked at bpatcher before, i kind of prefer to have everything in one patch though. i wonder how hard my original request would be to implement?


not sure this is what you're looking for, but you can retrieve your presentation rectangle with

[pattr @bindto scripting_name_of_your_object::presentation_rect]

and store it for reusing it when you need.

you don't even need to write it for every UI object, you can dynamically bind your pattr to one UI after another and store everything into a coll or whatever...

not sure this is what you're looking for, but you can retrieve your presentation rectangle with
[pattr @bindto scripting_name_of_your_object::presentation_rect]
and store it for reusing it when you need.
you don't even need to write it for every UI object, you can dynamically bind your pattr to one UI after another and store everything into a coll or whatever...

You can embed your [bpatcher] in the parent patch so it works more like [patcher] compared to an abstraction.

hi luke, i have used bpatcher a little before, so i get the concept. i just prefer working with everything in one window.

I really second Mike S on this feature...

 message has it's own utility and may be used as a trick to add/remove from the interface. But when you want, let's say 4 or more interface setups it gets really annoying to work with 

 for editing. And it is also annoying to have for each object the 

 message. Moreover, each time you reorganise your interface, you have to retype (or copy/paste) the 

However, it may be possible to write either an abstraction or a JS script to facilitate this kind of thing. I may have a look over it. I'll share what I'll come up with (if any).

Hi !
I really second Mike S on this feature...
I also use the presentation 0/1 message to adapt my interface. The hidden message has it's own utility and may be used as a trick to add/remove from the interface. But when you want, let's say 4 or more interface setups it gets really annoying to work with hidden for editing. And it is also annoying to have for each object the presentation_rect message. Moreover, each time you reorganise your interface, you have to retype (or copy/paste) the presentation_rect coordinates.

[feature request] object remembers previous presentation position