honestly i was expecting that max starts using true qt ui graphics. the similar way how it was implemented in Maya
at the same time i was scared on this so dramatic move, because i know how max built-in ui depends on WinApi
and what do we have finally?
we have a compromise solution – almost the same WinApi UI but drawn using Qt graphics.
this is not Qt controls! we (developers) don’t have access to qt parameters and signals.
but now we have a new UI solution to addition to win api, .NET, WPF, and true Qt… that already used in MAX
it’s a new system and more likely a new troubles
Well you didn’t really expect them to rewrite the UI system, did you? Who would rewrite all the thousands of tools, plugins and scripts that rely on WinAPI?
i hoped (but of course i understand how much work it is) that they make containers for all max controls how they did it for rollouts… this is how Maya developers did it for the most controls.
the thing what we have now is just new look of UI but with extra headache.
I bet they changed(converted) the UI just for supporting dpi. Why not WPF? I guess because they added Python and maybe next step they think they can make 3dsMax cross platform.
i want to ask :
IS NEW UI CONCEPT A STEP FORWARD, A STEP BACK, OR MARK TIME?
I vote wait and see… defo a step in the right direction and a huge amount of work to go to make it into what it needs to be.
i don’t believe i can be done evolutionary. it needs a revolutionary solution. which i don’t see with max 2017