Maxscript UI dialogue box issue in 3DS Max 2019.1

[Anonymous]

Sorry to take so long to get back. But I've been away for a bit. 
This is the problem that I've been having 

that is a screen grab of a window I have created in maxscript. 
You can see the text is too big for the dotnet.button that I created, at 125% text res
interestingly it does not scale up non-windows forms, and keeps the res as it should be.  Also the whole max form seems to have been scaled so the size of the window doesnt fit

 

Your post has been made into a thread by @hagen.deloss: here is the original thread 

[hagen.deloss]

Hi @Anonymous

I had no idea Maxscript was so robust a tool, thats really neat you are making your own UI using it. What is this particular UI being used for? It looks like some sort of camera controller?

I'm going to be honest, this is pretty outside my area of expertise... so you are thinking that your screen resolution settings are effecting the size of the typeface within your custom UI? I know that within UX design, there should be dynamic variables that change how any given UI appears depending on screen resolution. Is that something you are accounting for, or am I off base?

Again, sorry for my lack of experience in this particular field, I just reached out to a developer here that handles a lot of the UI programming, I will pass along what he says on this issue.

[Anonymous]

Yes it is a UI for the camera as I don't do a lot of modelling, mostly lighting and camera stuff. 
If you could also pass on that the problem does not exist if I used a dotnet object in a maxscript rollout. 
it really is isolated to this one situation where I am using a MaxForm gui. the only reason I used a maxform is because I wanted the transparency feature.  The button with the overscaled font is a dotnetobject "checkbox". The text doesn't seem to autoscale, but you can autoscale the box around it, it then puts out the rest of the gui and frankly looks terrible with lots of dead space.  Windows 10 has made the life of developers more difficult in many ways I imagine. 

[hagen.deloss]

Hi @Anonymous

I separated this thread from our previous one, as these issues seemed somewhat different 😄 

I have emailed someone in development with the details on the issue you are having with your MaxScript UI, I will let you know as soon as he gets back to me with further information. 

You mentioned that this scaling issue was present when you use the Maxform gui Transparency, does that mean you could implement this using a different system, without the transparency without these scaling issues? I'm wondering if there's a different tool that can get you transparency without this scaling issue, or is this the only tool for the job?

Haha sorry for the none specific questions, as I said, not my area of expertise 😛

I really appreciate your patience with this, talk to you soon!

[Anonymous]

I use regular rollout windows for most of my gui. What you see is part of much larger set of tools i made involving 25000 lines of maxscript. I wanted a window that i could "look through" (make transparent), regular rolllout windows cannot do this. Only winows forms have this facility  I instanciate a windows form object and set trigger events to drive my code which drives the physical camera. I use the maxform library. 

I extensively use dotnet tables, sliders, treeview, buttons, checkboxes in maxscript rollouts. Only this window has this scaling problem, and the most obvious one is this font.

The title bar also scales up with the screen scaling. Weather the window is semi transparent or not, the maxform result is the same. 

[hagen.deloss · Accepted solution]

Hi @Anonymous

Wow the UI you're working on sounds really extensive, thanks for the additional information that I can pass along! I was chatting with my colleague Jon and he mentioned the Autodesk Developers Network, you may want to look into leveraging that resource in the future. I also was thinking that if you had further UI questions that the Max programming forum may give you access to more focused advice. 

That being said, I chatted with @brentscannell briefly about this, who had this to pass along "Adopting an all Qt UI will help out with this issue, but I’m not sure you can do all that through Maxscript. I’ll ask around and get back to you and the thread."

I wish I knew more about this topic so I could help out further, but hopefully these resources point you in the right direction, and we will see what Brent uncovers 😄

Talk to you soon