Resolution autoswitch broken

[Leandro Jardim]

Hi Toni, I download beta 4, you did nice improvements on the GUI side of WinUAE. You work very professionally.

But the resolution autoswitch is not working very well yet, you have any plans for it, could it get fixed this version?

One other thing, could you remove the sunken bevel around the WinUAE window (just remove a flag in the window class)? Will look even better, guaranteed!

[Toni Wilen]

Originally Posted by Leandro Jardim

not working very well

...

Only possible reply to this kind of "report" is: it works as designed.

[Leandro Jardim]

Ah, sorry...

I use an interlaced 640x512 screen and when AmigaOS boots the line mode is always set to normal not matters what I do, even if I set it to "double", save the configuration and reset WinUAE.

Without the autoswitch it works normally.

Another thing I noticed, is that to be able to modify the resolution/line mode when the emulation is running I need to enter and exit WinUAE properties many times for WinUAE be able to "remember" the last change I did with it. One exit for each change I do on the controls.

[Toni Wilen]

Originally Posted by Leandro Jardim

I use an interlaced 640x512 screen and when AmigaOS boots the line mode is always set to normal not matters what I do, even if I set it to "double", save the configuration and reset WinUAE.

Will be fixed in next beta.

Another thing I noticed, is that to be able to modify the resolution/line mode when the emulation is running I need to enter and exit WinUAE properties many times for WinUAE be able to "remember" the last change I did with it. One exit for each change I do on the controls.

You need to first disable autoswitch, exit and enter GUI again and only then resolution/doubling settings work correctly without autoswitch overriding them. (Won't be fixed, not worth the trouble)

[Toni Wilen]

Originally Posted by Leandro Jardim

One other thing, could you remove the sunken bevel around the WinUAE window (just remove a flag in the window class)? Will look even better, guaranteed!

It isn't just a flag (actually that flag wasn't even set!) but positioning calculation needed changing.

Done in next beta