I'm curious, I loaded Perodika today and it said it had crashed during its last running and wanted to upload a bug report. So I played along and hit OK to submit. But it took me to a blank bug report form so I'm extremely curious what it thought was the problem ( as far as I know the program exited successfully last time I had run it. ) I closed it and started it again to see what was up but it didn't give me the message again so I can only assume it had found something? But not giving me any information on what it thought was wrong leaves me with being able to report nothing about that error. Perhaps that type of detection can be improved to give the user some type of info about the crash.
* I tried adding a blank exhibit (none existing file) today from the button bar on the screen and it gave me this error.
"That's a huge file; in fact, it's too big."
This should be changed to state file not found or something.
* Timestamps are to keep the info on the time the entry was last modified? If so it doesn't update this for me. I edit the entry but it still displays the time it was created. Is this why there is an "Edit Timestamp" option in the Entry menu? This seems tedious.
* There is some instability trying to Import a non existent file. It crashed the program giving a C++ error and corrupted the journal file. This is repeatable. The second time I did this it simply deleted all my entries but the journal file itself was readable. This should be like the exhibit importation. Perodika should catch the error and prevent the user from trying to import the non-existent file before it crashes.
I think you might want to do something to ensure that the journal file itself is more safe or protected from corruption in the event the program crashes. It would really be a pain for a user to write a lot and then have it possibly corrupted by a program crash. Perhaps backing it up somehow, I'm not sure.
I also feel strongly that you should allow users the option to label their journal entries instead of 1, 2, etc. It will make keeping it organized much easier.
* The error of losing the selection of the Event in the calendar and being able to click edit or remove and generating an error still exists. It should ask the user to select an entry or be grayed out.
* For the installer, add Back buttons so a user can change a setting without having to cancel the installation process and begin again.
* For un-installation KillPerodika.exe is still present as well as the folder for Perodika. I know most programs tend to leave these sitting around (registry entries too -shudder-) but it would be nice if it could remove and fix it's own entries. If nothing else removing the uninstaller and folder would be nice. And this is also slightly interesting but if you've run Perodika, crashed it you can't uninstall the main Perodika.exe file. I checked Processes tab but it's not running there at all. So I'm confused why it would give an error removing it. But having restarted the PC it allowed me to manually remove the Perodika.exe file. Hardly a very dangerous bug though. More an annoyance.