It contains a single piece once again, this time a much simpler SVG image, which should look like this:
[attachment=0]test.png[/attachment]
Try dragging that out of the piece palette and rotating it.
This test doesn’t involve any of our code. What this will test is
whether Batik’s own SVG viewer is able to render SVG correctly on your
system.
Here’s what to do:
Unzip the archive.
% cd batik-test
% java -jar batik-squiggle.jar test.svg
What you should see first is the splash screen for Batik’s Squiggle
viewer, followed by a window containing a rendering of the same image
from the last test.
I have the same issue that Guillaume reported with Vassal (Virgin Queen module) and retina-display macbook pro. Your standalone SVG test with the batik.jar seems to work correctly.
java -version on terminal gives me :
java version “1.6.0_37”
Java™ SE Runtime Environment (build 1.6.0_37-b06-434-11M3909)
Java HotSpot™ 64-Bit Server VM (build 20.12-b01-434, mixed mode)
But System Preferences Panel tell me I have java 1.7 - (build 1.7.0_13-b20)
I have the same issue that Guillaume reported with Vassal (Virgin
Queen module) and retina-display macbook pro. Your standalone SVG test
with the batik.jar seems to work correctly.
Thanks for your help!
Warmest regards,
Michael
I should mention that I am using:
OSX: 10.8.2
VASSAL-3.2.3-svn8552-retina-svg-macosx
Java:
java version “1.7.0_04”
Java™ SE Runtime Environment (build 1.7.0_04-b21)
Java HotSpot™ 64-Bit Server VM (build 23.0-b21, mixed mode)
That’s unexpected.
So, we have the standalone test working with Java 7, but not with
Java 6?
mgringo, do you see the text if you load this module with this build
of VASSAL?
java -version on terminal gives me :
java version “1.6.0_37”
Java™ SE Runtime Environment (build 1.6.0_37-b06-434-11M3909)
Java HotSpot™ 64-Bit Server VM (build 20.12-b01-434, mixed mode)
But System Preferences Panel tell me I have java 1.7 - (build
1.7.0_13-b20)
Start VASSAL and post the errorLog (you can find this under Help >
Error Log in the Module Manager). This will tell us which version
of Java VASSAL is running in.
2013-02-18 11:34:28,527 [0-main] INFO VASSAL.launch.StartUp - Starting
2013-02-18 11:34:28,532 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X
2013-02-18 11:34:28,532 [0-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_37
2013-02-18 11:34:28,532 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.3-svn8547
2013-02-18 11:34:28,957 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
So Vassal is actually using 1.6 (and Terminal too). I’ll look around and try to solve that.
Hum… Still no cigar. But Oracle tells me that I have the right Java
installed.
typing
% /Library/Internet
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -version
Gives me :
java version “1.7.0_13”
Java™ SE Runtime Environment (build 1.7.0_13-b20)
Java HotSpot™ 64-Bit Server VM (build 23.7-b01, mixed mode)
typing
% java -version
gives me the old one.
I am over my head with this one, I am afraid.
This means that Java 6 is found on your PATH before Java 7. The command
‘which java’ will show you the path of the java binary which is found
on your path. What does it say?
the JRE 7 installer doesn’t create proper symlinks for the java binary.
I have no idea why Oracle thinks it’s acceptible for the installer to
behave that way, since it leaves you with exactly this problem. They’re
essentially saying “our installer doesn’t finish doing its job”.
What’s the output now when you run each of the following:
which java
java -version
ls -l /System/Library/Frameworks/JavaVM.framework/Versions