-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
None
While fixing 5008045, it was noticed that
Win32GraphicsDevice.isDisplayChangeSupported() explicitly checks for screen 0.
This may be a bad idea for systems that set their primary display to something
other than the screen known as "0". We should instead check to see whether
the current device is the default for the local graphics environment. (5008045
includes a new helper method called isDefaultDevice() which can help in this
case.)
Note that we haven't verified that this is actually a bug (maybe the 0 check is
there for good reason), but I'm filing this anyway so that someone can
investigate this more thoroughly.
Win32GraphicsDevice.isDisplayChangeSupported() explicitly checks for screen 0.
This may be a bad idea for systems that set their primary display to something
other than the screen known as "0". We should instead check to see whether
the current device is the default for the local graphics environment. (5008045
includes a new helper method called isDefaultDevice() which can help in this
case.)
Note that we haven't verified that this is actually a bug (maybe the 0 check is
there for good reason), but I'm filing this anyway so that someone can
investigate this more thoroughly.