Switch to Multiple Screens Exception: Vassal 3.1.4 on Mac.

While trying to test multiple displays and windows, I ran into an unhandled exception. When trying to use the automated reporting method, it was unable to send a bug report.

Vassal 3.1.4, Mac OS 10.5.6, Java 1.5

What I did, although I don’t think the preliminaries really matter.

  1. Started Vassal and opened a module.

  2. Unchecked the “Use Combined Window” preference.

  3. Relaunched the module, now with separate windows.

  4. Changed my display configuration to have two displays. Vassal is left running.

  5. The main Vassal window ended up on the second display, and an unhandled exception occurred.

[code]08 May 2009 16:35:50.050 0 – Starting
08 May 2009 16:35:50.052 0 – OS Mac OS X
08 May 2009 16:35:50.052 0 – Java version 1.5.0_16
08 May 2009 16:35:50.052 0 – VASSAL version 3.1.4
08 May 2009 16:35:50.988 0 – Manager
08 May 2009 16:36:06.923 0 – Loading module file /Users/tar/Documents/Games•/Vassal/blackdeath.vmod
08 May 2009 16:36:06.925 0 – Loading module Black Death
08 May 2009 16:36:06.931 0 /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -Xms256M -Xmx512M -DVASSAL.id=1 -cp /Applications/VASSAL-3.1.4.app/Contents/Resources/Java/Vengine.jar -Xdock:name=Black Death -Xdock:icon=/Applications/VASSAL-3.1.4.app/Contents/Resources/VASSAL.icns VASSAL.launch.Player
08 May 2009 16:36:11.584 1 – Black Death version 1.1
08 May 2009 16:36:11.584 1

08 May 2009 16:36:40.826 1 – Exiting
08 May 2009 16:36:42.905 0 – Loading module file /Users/tar/Documents/Games•/Vassal/blackdeath.vmod
08 May 2009 16:36:42.907 0 – Loading module Black Death
08 May 2009 16:36:42.907 0 /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -Xms256M -Xmx512M -DVASSAL.id=2 -cp /Applications/VASSAL-3.1.4.app/Contents/Resources/Java/Vengine.jar -Xdock:name=Black Death -Xdock:icon=/Applications/VASSAL-3.1.4.app/Contents/Resources/VASSAL.icns VASSAL.launch.Player
08 May 2009 16:36:45.275 2 – Black Death version 1.1
08 May 2009 16:36:45.276 2

08 May 2009 16:37:32.354 2 – Exiting
08 May 2009 16:39:02.952 0 java.lang.ArrayIndexOutOfBoundsException: 1
at apple.awt.CWindow.displayChanged(CWindow.java:449)
at apple.awt.EventFactoryProxy$2.run(EventFactoryProxy.java:84)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
[/code]

Thus spake “tar”:

The only way we could catch that exception is with the global unhandled
exception handler, since none of our code appears in the stack trace.

My recommendation is to report the bug to Apple, since it’s a bug in one
of their classes.

I’m more interested in the problem you had with the Bug Dialog, as that’s
probably one of ours.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

On May 8, 2009, at 2:16 PM, Joel Uckelman wrote:

Well, I posted the ErrorLog on SourceForge. It has the stack trace
from BugUtils in it.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

On May 8, 2009, at 2:16 PM, Joel Uckelman wrote:

I plan on doing that.

It turns out that the bug doesn’t seem to actually stop things from
operating. After dismissing the bug reporter, things seem to work
fine, and windows can be placed on either display.

Hmmm.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)