In image editing mode, the Date field displays the "date modified," from the O.S. The field appears to be editable, but changes made to that date don't "take" - when you go back into edit mode, the unchanged date reappears.
I'm not sure if this ever worked - I don't recall ever trying to modify that date.
(BTW, the Reset file date to camera date does work, but the results aren't visible until you close, then re-open, the project.)
Interesting... This must have been broken since we bundled jAlbum with Java 11. In Java 9, they modified the default date-time pattern, adding a comma to separate date and time. This broke my logic. I should have ensured that a proper error message was printed at least, but that was not the case. jAlbum silently ignored the error
That's fixed it.
But it raises a philosophical question. If a feature has been broken for almost three years before anyone notices, do you fix it, or do you remove it?
It's certainly a question worth asking. Now, the user experience isn't complicated by these fields being editable, so I don't see any downside by allowing this ability. Also, one contributing reason why we haven't got bug reports on this could be that it seems to work - no error messages. It's only when you revisit the same image you see that the date change was ignored.
Yeah, in this case it's a low-cost option - it's not as if it's consuming vast swathes of screen real estate, or otherwise complicating the UI. There are some jAlbum options that I do wonder about, however....