-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
b51
-
x86
-
windows_xp
-
Verified
FullScreen feature is not working properly for some of the display modes on noddraw when the width and height of the display mode set is bigger than width/height of the current display mode.
I am getting all the supported display modes by calling gd.setDisplayMode(), when a frame is in fullscreen mode. For all the display modes whose width & height are bigger than the current display mode the fullscreen frame is shifted towards the left and occupies only 3/4 th of the screen. Hence it is not truely fullscreen. I am able to see the desktop on the right hand side of the screen.
This is reproducible on all builds on Win32 when running on noddraw mode. This is not reproducible on ddraw mode. This is reproducible on opengl mode since ddraw is disabled on opengl.
I have attached a sample test. Execute the sample test. You would see a frame in fullscreen mode with a button at the bottom. Click the button. the display mode of the frame changes in such a way that the new display mode's width and height are bigger than the current one. If the fullscreen frame does not occupy the fullscreen, the bug is reproduced. You can keep changing the display modes by repeatedly clicking on the button.
I am getting all the supported display modes by calling gd.setDisplayMode(), when a frame is in fullscreen mode. For all the display modes whose width & height are bigger than the current display mode the fullscreen frame is shifted towards the left and occupies only 3/4 th of the screen. Hence it is not truely fullscreen. I am able to see the desktop on the right hand side of the screen.
This is reproducible on all builds on Win32 when running on noddraw mode. This is not reproducible on ddraw mode. This is reproducible on opengl mode since ddraw is disabled on opengl.
I have attached a sample test. Execute the sample test. You would see a frame in fullscreen mode with a button at the bottom. Click the button. the display mode of the frame changes in such a way that the new display mode's width and height are bigger than the current one. If the fullscreen frame does not occupy the fullscreen, the bug is reproduced. You can keep changing the display modes by repeatedly clicking on the button.