MaxVer is likely a global variable introduced by one of the scripts you are using, it’s definitely undefined on my end. Might be more reliable to use the maxVersion output.
All I know is that I’m using update 1 and the issue seems to be fixed there, no idea what the ID of the fix is though.
I think it might be Vray or Phoenix FD that is registering it as they are the only plugins that I have installed as yet… I will take your advice and use MaxVersion() though.
I could see no documentation regarding the change to having global functions for event handlers, but I loaded an unmodified script for 2016 in 2019.1 and it worked perfectly.
What gives?
Still now I know of the problem I will still have to have conditional code based on (maxversion())[1] < 21000 and (maxversion())[1] > 19000 – except I wont ever be able to test it now as I never installed 2018… and max2019 has been upraded…
oh well. If I ever release my script the 2018 users can message me …
I’ve had the same issue with maxform based UI’s in max 2019. After installing the 2019.1 update the issue of non responsive dotnet controls went away.
Dotnet controls on rollouts and dialogs were not affected by the way.