WinUAE 4.3.0 beta series

[Solskogen]

Originally Posted by Toni Wilen

Does it become normal size if you click misc panel default button?

No

[Toni Wilen]

Which windows version? (Include exact build and/or release name).

I did test this using 4k TV with high DPI and it did work (even moving between monitors with different DPI) but it is possible it got broken with older Windows versions (pre-win10 1703)

[Solskogen]

This is Windows 10 1903 with all of the updates installed.
WinUAE 4.2.1 does not have this problem.

[Toni Wilen]

Originally Posted by Solskogen

This is Windows 10 1903 with all of the updates installed.
WinUAE 4.2.1 does not have this problem.

GUI scaling support was rewritten in 4.3.0, previous one fought against Windows 10 high DPI support, resulting in a mess..

Does http://www.winuae.net/files/b/winuae.7z work? (At least it works fine here in 4k resolution + 200 and 300 DPI. Except bottom buttons are currently slightly too large.). Wrong size is normal if display DPI was changed but "Set default" should always fix it.

[Solskogen]

Same problem there, but I found a workaround that I must do every time I start WinUAE.
Misc -> check Resizeable GUI. It stays the correct size even if I uncheck it.
It *might* have something to do with that I run a 150% scale rather than the 200% scale that is default in Windows on my setup.

[Toni Wilen]

Originally Posted by Solskogen

Same problem there, but I found a workaround that I must do every time I start WinUAE.
Misc -> check Resizeable GUI. It stays the correct size even if I uncheck it.
It *might* have something to do with that I run a 150% scale rather than the 200% scale that is default in Windows on my setup.

Strange. 150 also works fine here and resizeable GUI makes no difference.

Run with log enabled (for example -log command line parameter). Last 3 lines of log should be something like this:

Entering GUI idle loop
Requested GUI size = 800x600 (720x568)
Got GUI size = 1202x885

Which values do you get when a) size is wrong b) size is correct? Check also GUI font, size should be 8.

[Solskogen]

Entering GUI idle loop
Requested GUI size = 783x458 (720x568)
Got GUI size = 783x458

[Solskogen]

Try deleting HKEY_CURRENT_USER\Software\Arabuusimiehet in regedit. See if you can provoke the bug that way.

[Toni Wilen]

Originally Posted by Solskogen

Try deleting HKEY_CURRENT_USER\Software\Arabuusimiehet in regedit. See if you can provoke the bug that way.

It won't help. Set default will always reset all GUI variables.

Originally Posted by Solskogen

Entering GUI idle loop
Requested GUI size = 783x458 (720x568)
Got GUI size = 783x458

Interesting, it looks like Windows DPI value gets ignored. Perhaps you have some compatibility options set for winuae.exe? (right click, properties, compatibility)

(It still should work better but root cause should be found first)

[Tomislav]

Under Miscelaneous/Graphics API I have only DirectDraw. No D3D. In 4.2.1 are all 3 options (DD, D3D9 and D3D11).

EDIT: They are actually there, accessible with cursor keys, but drop down part is too small to see any option.

[Solskogen]

No compability mode is set either. If I delete the stuff from the registery I get this

Entering GUI idle loop
Requested GUI size = 800x600 (720x568)
Got GUI size = 800x600

[Toni Wilen]

GUI scaling partially rewritten yet again, now GUI elements are created using CreateDialogIndirectParam() reimplementation from ReactOS/Wine

- Above reported high DPI size issue should be fixed. (Default click still needed first. I'll plan to implement automatic size increase if font is too large compared to gui size)
- Misaligned GUI elements should be also fixed.
- List font setting is gone. Possibly back later.
- Weird multiple active GUI elements is not yet solved.

http://www.winuae.net/files/b/winuae.7z (official beta tomorrow if no new issues found)

[ross]

Originally Posted by Toni Wilen

GUI scaling partially rewritten yet again, now GUI elements are created using CreateDialogIndirectParam() reimplementation from ReactOS/Wine

- Above reported high DPI size issue should be fixed. (Default click still needed first. I'll plan to implement automatic size increase if font is too large compared to gui size)
- Misaligned GUI elements should be also fixed.
- List font setting is gone. Possibly back later.
- Weird multiple active GUI elements is not yet solved.

http://www.winuae.net/files/b/winuae.7z (official beta tomorrow if no new issues found)

Hi Toni, shift-F12 doesn't work anymore for me.
Quicstart A500 (512k+512k, KS13), S-F12 -> guru: (#00000002.00c01570, replicable), -> crash dump.
W10 Pro 1903

[Zarnal]

Crash confirmed with Windows 8.1 " Couldn't open Amiga.lib ".

[Toni Wilen]

Fixed (and GUI debugger is still unsupported). btw, that message has nothing to do with the crash. Always check previous working version.. EDIT: fortunately this was easy fix, someday it will become too incompatible..

Most multiple GUI elements being active at the same time -problem should be also gone.

EDIT: Flicker when switching panels is gone.

[DamienD]

Originally Posted by Toni Wilen

GUI scaling partially rewritten yet again, now GUI elements are created using CreateDialogIndirectParam() reimplementation from ReactOS/Wine

- Above reported high DPI size issue should be fixed. (Default click still needed first. I'll plan to implement automatic size increase if font is too large compared to gui size)
- Misaligned GUI elements should be also fixed.
- List font setting is gone. Possibly back later.
- Weird multiple active GUI elements is not yet solved.

http://www.winuae.net/files/b/winuae.7z (official beta tomorrow if no new issues found)

Hi Toni,

Yup, GUI / Configuration list now looks good again for me on my Windows 7 laptop

Originally Posted by Toni Wilen

Fixed (and GUI debugger is still unsupported). btw, that message has nothing to do with the crash. Always check previous working version.. EDIT: fortunately this was easy fix, someday it will become too incompatible..

Most multiple GUI elements being active at the same time -problem should be also gone.

EDIT: Flicker when switching panels is gone.

Only one GUI element being active at the same time still present; under "RTG board":

[Toni Wilen]

Yeah, I noticed it but I didn't mention it because it can affect any disabled element.

Should be fixed now.

But because it is SetWindowPos() that weirdly messes up focus state, perhaps I really need to delete and re-create each GUI element one by one after resize instead of trying to move/resize them one by one. There could be some other weird unexpected side-effects.. We'll see later..

[DamienD]

All good now, thanks Toni

[DamienD]

Hi Toni,

Twice today I've had WinUAE lock up when trying to quit using <CTRL> + <F11> from my "Classic WB Lite 3.1" .HDF.



I'll try to grab logs and a crashdump file; I know just saying the above isn't helpful.

Also, I noticed after loading / starting a game and then quitting; sometimes the WinUAE GUI is still there.

[Toni Wilen]

Remember that dumps are useless without using official beta versions. Wait until next official beta. (btw, there was GUI related double free and buffer overflow which can explain the problem. Was fixed few hours ago)