diff options
author | rhatcher <[email protected]> | 2012-11-29 09:11:07 -0600 |
---|---|---|
committer | rhatcher <[email protected]> | 2012-11-29 09:11:07 -0600 |
commit | 811e3791b98fea0dfa3b7d301cb532c54df8dc82 (patch) | |
tree | d9131c18c990c00c85e313d4ea6d2c50adf3b117 /src/newt/native/WindowsWindow.c | |
parent | f25b5c973150252af5c5fbf4ca87b03e2e9aee32 (diff) |
Fix for JOGL bug 629, and added new unit tests.
The change to AWTNewtEventFactory appears to fix the original issue
for AWTCanvas instances, and the TestNewtEventModifiersAWTCanvas
appears to work ok too. However, there are still issues with
NewtCanvasAWT and NewtCanvasSWT instances. These might be problems
in the test code, but there's also a good chance there are still
issues in the NEWT event delivery infrastructure. For the time being
I recommend that only TestNewtEventModifiersAWTCanvas be included
in routine unit tests.
The tests are defined in TestNewtEventModifiers, and the remaining
test classes extend it to define how the window and associated
GL drawing surface are created.
File ModifierMappings.txt is simply informational, and shows how
the modifier bits are laid out between AWT and NEWT. This possibly
should have been a spreadsheet.
Diffstat (limited to 'src/newt/native/WindowsWindow.c')
0 files changed, 0 insertions, 0 deletions