Hi.
I’m currently using mgear, but when I launched Anim Picker on my 4K monitor, the text size on the buttons became distorted.
I checked each module in AnimPicker, but I’m stuck because I can’t figure out which part to fix to resolve this.
If anyone knows how to fix this, I’d appreciate your guidance.
yes 
that is a know issue. The dpi scale is not properly handle. It is one thing I wanted to fix for long time. but couldn’t find the time to do it
Hi, Milio.
Thank you for your reply.
I’ll try the method you suggested right away.
Hi, Miquel.
Thank you for your reply.
I understand you are aware of the issue.
I will look into possible solutions in the code a bit more.
If you could address it when you have time, that would be helpful.
@Milio
Hi, Milio.
Thank you for sharing the solution with me the other day.
I tried the method you shared, but the issue hasn’t improved.
If there are any other areas besides Preferences that might be causing the problem, I’d really appreciate it if you could let me know.
Windows display settings are set to the recommended 150%.
@Miquel
Hi, following up on my previous report about the button label display bug.
We’ve done some more testing and can confirm that the issue only occurs with button labels generated from .pkr files. Other UI elements, like the ‘Space Transfer’ button, are still displaying correctly.
To help move this forward, we’d still be very interested in investigating the code.
Could you point us to the Python module responsible for parsing the .pkr files and generating the button layout?
Any guidance would be greatly appreciated.
some UI are not well supported with scaling. I also have a 150% scaling and get the same issues, but is not a critical bug.
For the picker you can adjust the text size to your particular scaling and it will work
@Miquel
Is it correct to understand that text size should be adjusted in the pkr file settings rather than through processing within the Python module?
it is not ideal, but is a workaround for the moment.
@Miquel
Thank you for your response.
I’ll try the workaround using pkr data.
If I find a good solution, I’ll post a comment.
The main problem is coping with the different configurations across people; some have their main display zoomed by 150% or 125%, while others have 100% but Maya preferences are scaled up. When I create the animpickers, I can ensure it is all readable in my setup, but other animators will have a different text size.
@Milio
You’re absolutely right.
Setting the zoom level to 100% did resolve the issue, but it also affects the display in other applications, so it’s not a fundamental solution.
While editing the pkr file allows for a temporary fix, I’d prefer to avoid having to prepare two versions—one for 100% and one for 150%—every time I create a pkr file.
Another sort of solution could be a little script that modifies the existing picker data in the scene.
@Milio
Indeed, scripting the editing of the PICKER_DATA node would solve the issue if we have the operator at the 4K monitor execute the process.
Thank you so much for exploring various solutions.
And maybe with mayaDpiSetting command in query mode it could be made variable in the tool?
cmds.mayaDpiSetting( query=True, mode=True )
