Windows 10, first observed with jAlbum 35. Confirmed with installing 36.

I was struggling with my own groovy script, so I tried one provided with jAlbum installation.

When trying to run unmodified "Correct image orientation" groovy script from 35 and 36 installations I am getting "groovy.lang.MissingPropertyException: No such property: processCount" exception.

After some troubleshooting I was able to strip script to a very simple code to reproduce an issue:

/* This script corrects the orientation of images that haven't been rotated properly by some software */
 
import se.datadosen.jalbum.*;
import se.datadosen.component.*;
 
var processCount = 0;
 
void processFolder(AlbumObject folder) {
        processCount++;
}
 
// Execution starts here
msg =
"This script corrects the orientation of images that haven't been rotated properly by some software";
 
processFolder(rootFolder);

Error will go away if I comment out

//processCount++;

After some Googling it seems be a known issue with certain groovy versions. The same code runs fine when changed from *.groovy to *.bsh

... or even better:

int processCount = 0;

I suspect ‘force of habit’ led to this particular oversight when changing from BeanShell to Groovy. It was a lot of fun for skin developers converting to Groovy too, but worth the effort.

There is one more tool that has the same error, 'Rename slide variables.groovy'.
Lines 17, 42 and 43 all have a 'var' before the variable name.

So, why not take out these tools of the list to avoid confusion?