Rodrigo

So in opening my main patch in Max7 I notice that all panels have defaulted to having a white border, even though in Max6 they have black. That will be a fun process, to chase all those panels down and manually change them all.

But in fixing other UI discrepencies, (umenu being wider than before), any bpatcher I opened and saved with Max7, pooped all over the looks I had set up for my objects (see screenshot). The top modules are what it used to look like in Max6, and the bottom modules are what it looks like in Max6 once opening/saving the file in Max7.

So either I manually alter every file in my patch (hundreds!), or I have to live with this mess of a UI.

(On top of which my patch crashes in Max7 the moment I turn on audio...)

So in opening my main patch in Max7 I notice that all panels have defaulted to having a white border, even though in Max6 they have black. That will be a fun process, to chase all those panels down and manually change them all. 

(On top of which my patch crashes in Max7 the moment I turn on audio...)


max7-radically-changing-ui-look-when-opened-in-max6

In playing with it a bit more it appears that saving a file in Max7 makes it impossible to NOT have rounded corners for textbutton in Max6.

If you want to guarantee Max 6 appearance, we recommend authoring your patches in Max 6. While patches made in Max 7 will largely work and look basically okay in Max 6, these levels of GUI backward compatibility are not supported.

Regrading your crash, please send to support (at) cycling74.com, with an example, support information, and any relevant steps to reproduce.

Ok, good to know. Once I get it working in Max7 I'll just tweak/work there.

I'll send an email with crash report to support.

Fairly valid concern. The new UI really does make old carefully created UIs look quite dodgy and even confusing in some cases.

I agree. It's a pity that the UI looks so different and makes older patches very bad to read. It would be nice to have at least one style that is close to the old max - black text with bright background.

Working From Max 6 but yes opening in 7 drastically changes ui stuff. Rslider and TextButtons with transparencies. Maybe we'll have to make max6 and max7 versions of things for a while?

So far most of the live.objects look the same in both, but I've not found a good solution for umenu yet.

Also the spacing for the buttons in a preset object are different. I havent had problems with borders, but when sharing a live patch, one has to make separate versions for max 6 and max 7 users.

Would it make sense to have a script that alters settings for backwards compatibility, which one could add to max 7 patches so that max 6 users could still see them properly?

Also the spacing for the buttons in a preset object are different. I havent had problems with borders, but when sharing a live patch, one has to make separate versions for max 6 and max 7 users. 

Would it make sense to have a script that alters settings for backwards compatibility, which one could add to max 7 patches so that max 6 users could still see them properly?


You could set color and inspector attributes with messages.

So you could use a loadbang / loadmess / or live.thisdevice to send gui stuff to your objects on startup but that is definitely a pain.

Ernest
You could set color and inspector attributes with messages.
So you could use a loadbang / loadmess / or live.thisdevice to send gui stuff to your objects on startup but that is definitely a pain.


Yeah Im trying to get excited about making it

Why isn't it possible to set up a default template that Max would use to open any patcher not created with Max 7? Seems like it should be possible for Cycling 74 to implement. Unfortunately, simply editing or replacing the original "Default Max 7" template has no effect on the look of patches that are opened in Max 7.

I agree phillip, that is why I feel so unexcited about making it.

Max7 radically changing UI look when opened in Max6