UI scaling changes from latest 2025a prerelease to official 2025a release

Hi, I spent MANY hours to get my GUI running in 2025a - I included many changes to fix all the scaling issues of ui elements. I was always using the latest prerelease to implement and test these changes. Now after the "big mathworks crash", I finally could download the official 2025a release. And I notice that the scaling of ui element has completely changed and everything is messed up again. This is driving me crazy! Why are there prereleases if things are again changed in the last second?

I hope this is just a dpi scaling thing that can be fixed easily. Anyone maybe with some hints where to search?

Thanks!

[William Thielicke]

New scaling in 2025a

Old scaling in 2024b (and 2025a latest prerelease)

[William]

I am in contact with the support. I think, the reason for the different scaling has something to do with different scaling of character units:

MainWindow = figure('numbertitle','off','MenuBar','none','DockControls','off','Name','Test...','Toolbar','none','tag','hgui','visible','on','WindowState','maximized');

set (MainWindow,'Units','Characters');

Figure_Size = get(MainWindow, 'Position')

get(0,"ScreenPixelsPerInch")

get(0,"ScreenSize")

close(MainWindow)

This gives different results for Matlab2025 and previous (pre)releases.

Accessibility Text Scaling is at 100%, Screen scaling is at 100%, set(groot,'DefaultUicontrolFontSize',8) has no effect.

Answer 1

[Adam Danz]

There's a known issue using Accessibility Text Scaling on Windows that affects UI Components in R2025a and some earlier releases. The workraound is described in this report: https://www.mathworks.com/support/bugreports/details/3632276

If that does not solve the issue please work with Tech Support.

[William Thielicke]

Thanks, but my setting is and has always been at 100%.

[William Thielicke]

... and I have not changed my computer or any settings of my computer. Something has changed between the last prerelease and the official release.

[Adam Danz]

I spoke to several other developers in this area to see what else might be the issues. If you are using character units and running this line below fixes the issue, then it's a known issue that is being addressed in an update release.

set(groot, 'DefaultUicontrolFontSize', 8)

Otherwise, it's best to work with tech support so we can gather some more info.

[William]

Hi, I am using character units, but the line of code you gave does not have any effect. I have opened a support ticket, linking to this thread. These are the files responsible for making the GUI:

https://github.com/Shrediquette/PIVlab/blob/main/PIVlab_GUI.m

and

https://github.com/Shrediquette/PIVlab/blob/main/%2Bgui/generateUI.m

[William Thielicke]

@Adam: Tech support doesn't really seem to give this issue much attention (I fear there are probably a lot of support cases at the moment), it is taking 2 weeks without new suggestions on how to solve this. No new suggestions from your colleagues maybe? I think it all comes down to the code given here:

https://de.mathworks.com/matlabcentral/answers/2177368-ui-scaling-changes-from-latest-2025a-prerelease-to-official-2025a-release#comment_3334761

I am of course absolutely willing to change my code if we find a solution that's future proof and backwards compatible (and ideally, I don't have to change the code manually for 563 uicontrols).

P.s.: My ticket nr is 07864694

[Adam Danz]

Hello @William Thielicke,

I don't have access to your ticket right now so I don't know what tech support has tried so far.

I started investigating the code snippet you pointed to in both R2025a and R2024b.

1. I was able to reproduce the difference in the window position values between R2025a and R2024b when using centimeter units with maximized size.
2. To simplify the call to figure(), I removed the inputs and set defaults instead. That didn't change the behavior but it ruled out the possibility that some of the other properties were interfering.
3. By placing a drawnow and a pause of 1 second before querying the figure position, I was able to match the values between R2025 and R2024b. The drawnow alone did not solve the problem. I did not experiment with smaller pause values-- the key is having a long enough pause for the figure to fully render. If I remove the "drawnow; pause(1)" line, the mismatch between 25a and 24b returns.

Does the drawnow + pause(1) line make a difference for you?

defaultToolbar = get(groot,'DefaultFigureToolBar'); 
defaultWindowState = get(groot, 'DefaultFigureWindowState'); 

revertDefaults = onCleanup(@()set(groot,'DefaultFigureToolBar',defaultToolbar));
revertDefaults(2) = onCleanup(@()set(groot,'DefaultFigureWindowState',defaultWindowState));

set(groot, 'DefaultFigureToolBar', 'none', ...
    'DefaultFigureWindowState', 'maximized', ...
    'DefaultFigureWindowStyle','normal')

MainWindow = figure(); 
MainWindow.Units = 'centimeters';
drawnow; pause(1)  %< ------------------ this is key
Figure_Size = get(MainWindow, 'Position')
get(0,"ScreenPixelsPerInch")
get(0,"ScreenSize")
close(MainWindow)

[William Thielicke]

Dear Adam, oh that is interesting, I will try immediately when I return from my travel. In the meantime I got a final reply from the support, stating:

"Unfortunately, I have to tell you that this is a bug that was introduced between R2025a prerelease and R2025a, while fixing something else. Our developers are working on fixing this as soon as possible, but until then, we can't provide a simple workaround. I'm very sorry for the inconvenience that this causes for you."

[Han Geerligs]

Hello I have the same issue when using uifigure dialogs with 'characters' units.in R2025a.

I was wondering when the fix from development is expected to be released.?

kind regards,

--Han

[Steven Lord]

You should follow the bug report Adam linked to in his answer. When anything significant changes (a new workaround added, a release in which the bug is fixed becomes available, etc.) the bug report will be updated and users following it will be notified.

We don't always send out notifications when bug reports get modified if the change is something like a typo fix, but "this bug is fixed in release X" would cause a notification to be sent.