Window size changed after using "Enable Fullscreen"
Versatile Commodore Emulator
Brought to you by:
blackystardust,
gpz
Menu
▾
▴
1 Attachments
#695 Window size changed after using "Enable Fullscreen"
x64sc 2.4.24 r30286M (GTK+ AMD64/x86_64 Linux glibc 2.21 GCC-5.2.1)
See attached image. If I press Alt-D to enable fullscreen and then press it again to go back to window-mode, the window size has changed (this is the part I consider a bug, if unclear).
same here.... iirc i tried to fix this a while ago with little success. i think the problem is this:
the gui code keeps track of the windows position and size, so it can save those to the config file (and restore later). the same values are used to restore the window to its original dimensions when coming from fullscreen. however, apparently "resize" and/or "move" events are still being processed while the window is being resized to fullscreen, the problem being the "alt+d" hotkey. this problem is probably related to the fact that "alt+d" is not a blocking operation as a whole (the handler returns to the event loop before going to fullscreen is completely done, meaning you can trigger another event before the previous one finished. - also see https://sourceforge.net/p/vice-emu/bugs/491/
Last edit: gpz 2015-12-16
Confirmed.
This also seems to be related to the 'keep aspect' function. If this is disabled, the problem doesn't occur in my setup (untick Settings -> VIC-II -> Keep Aspect).
Will look into it - maybe over the upcoming holidays.
any news?
a jolly yearly bump!
Another bump. Still an issue in x64sc 3.1 r34159 (GTK+).
Since pottendo is inactive ( https://sourceforge.net/p/vice-emu/code/34276/ ), reassign? Is there any workaround suggested? (For now I have run the Windows build in wine instead. Crazy? Yes. But it has worked for 2 years...)
On my box, Debian 9.3 with Gtk+ 2.24.31, running the Mate desktop, I can't reproduce this bug. But I've seen it in action on other distros/WMs.
It would be nice to get this fixed before the final release of all the old UI's. But who's going to do the work? Our time is mostly dedicated to building a proper portable Gtk3 UI.
I'll assign this to myself for now, though my time is limited when it comes to this. I'd also have to find a setup where this bug actually triggers (perhaps an Ubuntu VM). But it will be a low priority bug to me.
i can reproduce it here.... and i also already spent quite some time on trying to fix it. it just wont happen without a significant rewrite of the whole UI. ie never. wait for GTK3 :)
old GTK2 will get removed after 3.2