aboutsummaryrefslogtreecommitdiff
path: root/src/fadable-box.vala
diff options
context:
space:
mode:
authorMihai Moldovan <ionic@ionic.de>2023-08-30 08:35:08 +0200
committerMihai Moldovan <ionic@ionic.de>2023-08-30 09:46:26 +0200
commit9a8c29ddd12ca3e3733a3d23f74ef138bd0d637b (patch)
tree9d9dd43a153d45f0271acf3975edb5f20d2e5631 /src/fadable-box.vala
parente4e7bde556930467243a541f2e3359c9535d7c1c (diff)
downloadarctica-greeter-9a8c29ddd12ca3e3733a3d23f74ef138bd0d637b.tar.gz
arctica-greeter-9a8c29ddd12ca3e3733a3d23f74ef138bd0d637b.tar.bz2
arctica-greeter-9a8c29ddd12ca3e3733a3d23f74ef138bd0d637b.zip
src/arctica-greeter.vala: fix tiny main window on startup.
3a5ca24831d1b4a74af6cfd5c5cc2a42b5787aeb backported a commit calculating the really needed screen size more correctly as a prerequisite for additional multi-display support (span and zoom modes) from Slick Greeter (5d39cade1f70ffe0a9bc38ad0b405bb55d98a505), but unfortunately missed crucial code in src/arctica-greeter.vala. While the realize call on main_window should be harmless, calling setup_window on it actually leads to the main window resizing to the actual size that was queried via GDK. While setup_window is being called as part of the main window creation, the first call just skips resizing it (for some reason). Subsequent calls, which are *mostly* triggered through changes in the actual display configuration (hardware or software), then have main window recalculate its size (and updating the background). Honestly, we could just rip out the whole do_resize logic and always resize, since with these changes, we're forcing a resize on startup anyway. Not doing so leads to the nasty bug this commit fixes. However, to keep Slick Greeter's and our code more in sync (to make future backporting easier), let's keep it like this for now. Fixes: https://github.com/ArcticaProject/arctica-greeter/issues/47
Diffstat (limited to 'src/fadable-box.vala')
0 files changed, 0 insertions, 0 deletions