We’ve accumulated enough bug fixes over 3.2.8 now to make another release worthwhile:
10594: Max heap estimate sometimes too low for image tiler on Mac OS X
10590: Cards painted in wrong location when Deck is sent after using “Draw specific cards” but without drawing cards
10518: Text is not antialiased in chat pane on Linux
10493: HTMLCharts do not follow anchors
10468: VASSAL.sh doesn’t work if path includes spaces
10369: Windows installer doesn’t find older installs on 64-bit systems
10158: UnsatisfiedLinkError: Can’t find dependent libraries via MemoryUtils.getPhysicalMemory
9897: Mac bundle fails to find non-Apple JVMs
9833: UnsatisfiedLinkError because JNA DLL cannot be read
The bulk of these are platform-specific bugs: 9897 and 10594 affect only Macs. 10518 affects only Linux. 10468 affects systems which aren’t Windows. 9833, 10158, and 10369 affect only Windows.
The joint fix for 9833 and 10158 solves them by removing VASSAL’s dependency on JNA. We never determined why some Windows users were having a problem with the JNA DLL, but now we don’t need to.
Of these, the fix most in need of testing is the one for 9897. We’ve changed the launcher in the Mac app bundle to look for Java 7 before and in addition to Java 6. (The old app bundle did not look for Java 7 at all.) We’ve heard from few users regarding this change. It would be helpful to hear from more Mac users whether this works properly before we inflict it on them as a release.
The current build as of writing this is 3.2.9-svn8905. As always, builds are here:
It would be helpful to hear from more Mac users whether this works properly before we inflict it on them as a release
It seemed like I launched VASSAL and then the window went away. On the second time opening the application, it loaded. Nothing that I could see in the Mac Console for the first launch.
It seemed to pick up my 1.7 VM:
2013-11-11 20:31:32,410 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-11-11 20:31:32,415 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.9
2013-11-11 20:31:32,415 [0-main] INFO VASSAL.launch.StartUp - Java version 1.7.0_45
2013-11-11 20:31:32,415 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.9-svn8905
2013-11-11 20:31:32,667 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
It would be helpful to hear from more Mac users whether this works
properly before we inflict it on them as a release
It seemed like I launched VASSAL and then the window went away. On the
second time opening the application, it loaded. Nothing that I could see
in the Mac Console for the first launch.
It seemed to pick up my 1.7 VM:
Thanks. Did you try opening a module? We’re trying to determine the
cause of poor graphics performance on some Macs with Java 7. It
would be helpful to know whether (1) you’re seeing normal performance,
and (2) what kind of Mac you have (in particular, what kind of graphics
card).
Last login: Tue Nov 12 12:54:03 on ttys001
Zoltan-MacPro:~ zgrose$ cd ~/Downloads/compat-image
Zoltan-MacPro:compat-image zgrose$ ls
Test.class Test.java
Zoltan-MacPro:compat-image zgrose$ java Test
opaque type == 1
translucent type == 3
Zoltan-MacPro:compat-image zgrose$ java -version
java version “1.7.0_45”
Java™ SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot™ 64-Bit Server VM (build 24.45-b08, mixed mode)
Zoltan-MacPro:compat-image zgrose$
3.2.9-svn8963 is a new release candidate build for 3.2.9. It contains some fixes for problems in the previous build with incorrectly writing prefs files and incorrectly setting colors in the chat pane, as well as several problems with the construction of the Mac bundle.
Note that work on the Mac bundle for 3.2.9-svn8963 is not complete; what you see when you open the .dmg is a work in progress and is the last remaining bit of work for 3.2.9.