aboutsummaryrefslogtreecommitdiff
path: root/nestedvm.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2017-09-30 22:02:39 +0100
committerSimon Tatham <anakin@pobox.com>2017-09-30 22:02:39 +0100
commitf03e8d30a038f740ea0bfe21474de5df69093893 (patch)
treee9c76282573f5e7e6b610326c49d74920dd4486d /nestedvm.c
parent4cf2241f4f74620709ae12ce76e1b601353515b3 (diff)
downloadpuzzles-f03e8d30a038f740ea0bfe21474de5df69093893.zip
puzzles-f03e8d30a038f740ea0bfe21474de5df69093893.tar.gz
puzzles-f03e8d30a038f740ea0bfe21474de5df69093893.tar.bz2
puzzles-f03e8d30a038f740ea0bfe21474de5df69093893.tar.xz
Fix changing puzzle size in a maximised GTK3 window.
While working on the Net scalability today I noticed that changing preset from (say) 13x11 to 5x5 in GTK3 Net while the window is maximised does not have the desired effect (that being that, since the maximised window does not change size, the new puzzle size is instead scaled to fit neatly in the existing window). A git bisect suggests that this was a side effect of commit 8dfe5cec3; it looks as if there was a useful side effect of setting fe->area as the 'geometry widget' for fe->window, namely, that any attempt to resize the window thereafter (even if it had no effect on the window size) would trigger a configure event on the geometry widget, so we'd get a notification of our new size even if it was the same as our old size. But that 'geometry widget' feature is deprecated, so I have to work around it another way. Fortunately, I've found a fallback event that still does occur, namely "size_allocate" on fe->window. So I'm trapping that as well and using it as an indication that a configure event won't be forthcoming.
Diffstat (limited to 'nestedvm.c')
0 files changed, 0 insertions, 0 deletions