Ahhh! Very close now. After an hour of thinking yesterday, I finally figured out how it could all logically work. On a one page “napkin” (a napkin of course is the note-taking material preferred by most eccentrics) I mapped out how the buttons would interact with the active Organize info, the Last Processed Organize Info (used with the Cancel button) and the Last Saved Organize Info (used with the Reorganize button). And I would not have to save files with (_AO, _SO, and _IO) appended on them, which is good since this didn’t seem logical anyway. Instead, I would only have to warn the user when they might be overwriting a file they might not want to. For example, if Auto Organizing after loading a Behold file, all the Behold file customizations would be lost if the Auto Organized file is saved over it.
But the nice thing is the user of Behold will not have to worry about these details. Only I have to in order to get this right. I think this will feel quite natural the way I’ve done this.
I didn’t realize how much trouble these buttons would cause. They are needed and it is this Organizational functionality that will differentiate Behold from everything else. It was almost a year ago on Oct 30 that I started to work on them, and up to now this has been a major stumbling block.
It took only a few hours to program the button interaction. While at it, I also redid the file saving logic for Behold files as I outlined above. Works great! Love it!