JPEG Saver 5.40
Published
This is another release that improves things without adding much. It fixes a couple of bugs too.
Better logging
Logging was something that JPEG Saver could do, but it was very limited and inefficient. For this version I have made it more efficient and more capable, so I can actually make more use of it in the future.
Because of this, I have added the existing logging options that were previously only available by editing the config file into the debug dialog. You can set the log file location, enable logging of image/video loading and transitions, and toggle logging altogether.
You can now also view the log from the current run onscreen using a text file item with the filename set to "#log". It will show the last 50 entries, which should hopefully be enough.
The main logging toggle in the debug options dialog enables and disables logging to the file, but entries are still added to the log held in memory. This means the text item will still display entries onscreen when logging to file is turned off.
I don't expect the log file to be much use to end-users, but it should help me with development. Very little is actually logged in the released versions of JPEG Saver because the debug log output is not compiled in.
Better caching
In my testing I found that loading images from the cache was quite fast, but saving them was not so good. In this version I have made saving them faster and also improved the performance of the functions that manage the list of cache entries.
If you have logging of image loading enabled, the log entry will now say if the file was loaded from the cache. The new logging code is already proving to be useful.
Bugs
Now that the list of background images is stored in the main database, a new bug has emerged. The images from sub-folders of the background images folder were being displayed as foreground images. This was easy to fix, but I hadn't noticed it in my initial testing.
Some changes to the database code in a recent version also introduced a new bug to the slideshow mode, where a new database was being created but then not being used or deleted. This might have also affected new installations of JPEG Saver, but it was more obvious in slideshow mode.
Bottom of page
You can download the installer from the downloads page.