Posted 25 December 2012 - 08:46 AM
:facepalm: I just realised, I do get that error message in my logs, but it's largely meaningless; it prints if the call to mkdirs() fails, which it does if the directory already exists. It doesn't interrupt code flow, though, so it shouldn't be a critical error. I'll fix the logic to check for the directory already existing in the next version, so the error is not printed uselessly.
Is the BioLock actually not working, or did you see the error message and assume it wouldn't? If it's crashing, or not working, I'd expect there to be another error logged after that.
:edit: no time to apply the changes across all versions and package an update, but I've added checks for if the directory already exists, so it should print the error now only if it doesn't, or if a file exists with that name. I also went through and cleaned up the hard-coded "/" characters used in building paths, using File.separator and File.separatorChar instead; Windows is, in my experience, very tolerant of "/" instead of "\" in paths through it's high-level file routines, but it seems like a cleaner way to go, regardless.