I've been using jalbum and Turtle with no problem for years on Win 7 Pro x64. However, today I tried to install the latest Turtle update, and it didn't work.
I used both the "standard" method (within jalbum), and then I tried unzipping it into the skins folder in my roaming folder (rather than the skins folder in the jalbum install folder, where others are located).
This is the error message I got:
An unexpected error occurred. Please see detailed description below:
java.lang.RuntimeException: bsh.ParseException: Parse error at line 59, column 93. Encountered: Trebuchet
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
Caused by: bsh.ParseException: Parse error at line 59, column 93. Encountered: Trebuchet
... 12 more
Sorry, but I don't know what the "12 more" are.
Using the jalbum Update notification to install, first it looked like the skin was installing OK, but as soon as the installation was done, the error message appeared, and Turtle was completely gone from my list of skins.
Of course I had jalbum closed when I tried the "manual" install, but the same error message appeared when I opened it.
By the way, I've tried it on two Win 7 Pro x64 machines; the result was the same on both.
Yes, 5.6.1 has worked fine since the day it came out.
I always save a backup of my folders before updating anything, so I merely installed my backup.
Version 5.6.2 certainly doesn't work with 11.6.17 on my machines for one reason or another. Laca is an expert in the jAlbum environment, though, and my guess is that he'll find a solution if there is one.
I'd contend that when he says the "Min. jAlbum version" is 11.6.17, he expected it to work. Unless, of course, he merely forgot to change the entry on the website. That's fine, too.
As for my version being old, the reason I've stuck with it is that, frankly, I only use jAlbum once or twice a year. The version I have, and Turtle version 5.6.1, meet all of my "creative" and "technical" needs.
When I see a Turtle update that (in this case "allegedly") works with my version, I basically click the update button out of habit rather than need.
In any case, as always, thank you very much for taking the time to reply to my call for help.
I'd contend that when he says the "Min. jAlbum version" is 11.6.17, he expected it to work. Unless, of course, he merely forgot to change the entry on the website.
It's also buried in the skin properties file - that's what triggers a warning if you load a skin with a version of jAlbum that doesn't support it.
This wouldn't be the first time that a skin developer has unwittingly used some new feature in jAlbum, forgetting that the skin would blow up in an earlier version. I think we've all done it at one time or another. I sometimes code things to a beta version of jAlbum, and have to remember that I can't release the update until jAlbum catches up. Tough to test, too, especially in Windows, which does not like having multiple versions of an application floating around.
Once Tiger stabilizes a bit, you might find that it's enough of an improvement to warrant a license update (it really does require jAlbum 14). The page responsiveness might be worth the price of admission.
I see Laca has written Tiger as a replacement for Turtle, so maybe he won't want to invest the time investigating "my" problem.
Anyway, as I've said, considering my limited requirements, I'd say that at my age (70), about the only thing that would justify an update is if it includes a component to make me 30 or so years younger .
I guess this error happened because Tiger skin has changed some settings, and when you get back to Turtle it triggers this error. However Turtle 5.6.2 alone supposed to work with 11.6.17 (18). You can look for the jalbum-settings.jap in the album's folder and remove the line with "Trebuchet", or the text right to the equation sign in a simple text editor.
Yep, I agree, but now I tried, and could not reproduce the error when switching back. Turtle properly fell back to its defaults when something was in conflict. It would be great to see the jalbum-settings.jap of the album in question - perhaps that could help.
Uh, I see now, it seems I run the SkinModel creator tool which has left a "plugins" folder. And unfortunately this tool has left an error in the java file. All you need is to remove the "plugins" folder from the skin. I will fix this soon.