Keyboard NullPointerException fix #6

Merged
merged 1 commit into from Jan 26, 2013

2 participants

@jhauberg

Application would crash on start, so i figured i'd better open a pull request even though it's a tiny fix :)

@andykorth andykorth merged commit 2c3a639 into andykorth:master Jan 26, 2013
@andykorth
Owner

Oops. Thanks a lot!

@Robmaister Robmaister pushed a commit that referenced this pull request Nov 22, 2013
@thefiddler thefiddler Added workaround for issue #6
The issue is that some display devices report a BitsPerPel value of 0.
It is not clear whether this is a bug in WinDisplayDevice.cs or some
strange windows issue. The implemented workaround adds an entry to the
debug log and hardcodes BitsPerPel to 32 whenever this condition is
encountered. More investigation required.
a4f125f
@Robmaister Robmaister pushed a commit that referenced this pull request Nov 22, 2013
@thefiddler thefiddler Switch to EnumDisplayModesEx
Use EnumDisplayModesEx instead of EnumDisplayModes. This might help
with issue #6.
21a1ca8
@Robmaister Robmaister pushed a commit that referenced this pull request Nov 22, 2013
@thefiddler thefiddler Workaround for issues #4 and #6
GraphicsMode.Default used to be set to
(DisplayDevice.Default.BitsPerPixel, 16, 0, 0, 0, 2, false) for improved
compatibility with older systems. However, this appears to be causing
issues with specific modern GPUs. Switch the default mode to (32, 24, 8)
until a more proper solution can be found.
03c04fd
@AdamsLair AdamsLair pushed a commit that referenced this pull request Jan 24, 2014
@thefiddler thefiddler Made DPI-awareness configurable (issue #6)
It is now possible to indicate that an application is not DPI-aware. In
that case, OpenTK will let the operating system handle DPI scaling. This
results in worse visuals (pixel doubling) but allows non DPI-aware
applications to continue working.
1475b3d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment