Increasing resolution in fullscreen results in the right and bottom sides not being updated properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Fix Released
|
Low
|
Unassigned |
Bug Description
I was clicking around, verifying bug 1159968 / bug 1130905 / bug 1137765 was gone, when I noticed this odd behavior:
1. Go to options and switch to fullscreen with a small resolution (for instance 800x600).
2. In fullscreen, go back to options and switch to a larger resolution (for instance 1024x768).
Expected result:
The whole window is now rendered according to the new resolution.
Actual result:
While the content scales up to fit the new resolution, parts of the right and bottom side are not rendered. If you are lucky enough to hit the buttons in those areas, they are in fact there, they're just not being drawn. Looks like it simply keeps rendering according to the smaller resolution, not bothering with the additional content.
(To escape, go to options, select a lower resolution again and move the cursor down while clicking, hoping to hit the Ok button to change it back.)
At first I feared this was another regression, but I was able to reproduce it on build17 as well, so it's apparently been here for a while. If someone has a fix for this in by build18, that would be nice but feel free to reassign.
Widelands r6638 on Ubuntu 13.04.
Related branches
- Tino: Approve
-
Diff: 644 lines (+154/-171)13 files modifiedsrc/editor/editorinteractive.cc (+1/-1)
src/graphic/graphic.cc (+79/-73)
src/graphic/graphic.h (+26/-11)
src/graphic/text/test/render_richtext.cc (+1/-2)
src/logic/map_info.cc (+1/-2)
src/logic/ware_descr.cc (+1/-1)
src/notifications/note_ids.h (+2/-0)
src/wlapplication.cc (+18/-60)
src/wlapplication.h (+1/-6)
src/wui/interactive_base.cc (+14/-10)
src/wui/interactive_base.h (+8/-3)
src/wui/interactive_player.cc (+1/-1)
src/wui/interactive_spectator.cc (+1/-1)
Changed in widelands: | |
milestone: | build18-rc1 → none |
Changed in widelands: | |
status: | Fix Committed → Fix Released |
In my opinion this should be fixed by using the correct native display resolution in fullscreen mode and disable the resolution list when fullscreen is enabled.