Any ideas as to what kind of things might have broken under 3.2.14 that were working fine in 3.2.13?
I know you all need more specifics to really help me out, and I’ll probably have to go through the laborious processes of stripping out and adding in bits of my module until I pin down the cause, but what I’m really hoping for right now is a brief summary of what the update notes for 3.2.14 mean. What kind of functions have been altered. Those update notes are way over my head.
Briefly, my module crashes when trying to implement a single-click series of processes that usually takes a good few seconds to grind through, in which a few pieces are delected, a lot of decks are shuffled, and a piece layer is changed. I’m guessing it’s the shuffling?
Sorry for the useless post. Crying baby and work means I’m a bit rushed.
I also get a crash when shuffling a deck in a module that worked fine in 3.2.13.
The crash can be reproduced in a new module with only one deck with “re-shuffle via right-click menu” enabled.
java.lang.NullPointerException: null
at VASSAL.counters.Stack.insertChild(Stack.java:207) ~[Vengine.jar:na]
at VASSAL.counters.Deck.setContents(Deck.java:819) ~[Vengine.jar:na]
at VASSAL.counters.Deck.shuffle(Deck.java:758) ~[Vengine.jar:na]
at VASSAL.counters.Deck$6.actionPerformed(Deck.java:1040) ~[Vengine.jar:na]
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995) ~[na:1.6.0_26]
I also get a crash when shuffling a deck in a module that worked fine in
3.2.13.
The crash can be reproduced in a new module with only one deck with
“re-shuffle via right-click menu” enabled.
Code:
java.lang.NullPointerException: null
at VASSAL.counters.Stack.insertChild(Stack.java:207) ~[Vengine.jar:na]
at VASSAL.counters.Deck.setContents(Deck.java:819) ~[Vengine.jar:na]
at VASSAL.counters.Deck.shuffle(Deck.java:758) ~[Vengine.jar:na]
at VASSAL.counters.Deck$6.actionPerformed(Deck.java:1040)
~[Vengine.jar:na]
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
~[na:1.6.0_26]