While not obsolutely essential, I would use the Close icon from toolbar if it were located next to exit.
I have a big debate going on in my head over what icons to include and what not to. Too many are no good. Too few are no good. I could allow users to customize them, but most find that confusing and would prefer a fixed setup selected for them.
Now that you've got me thinking about it, maybe a Close icon would be more useful than the Exit icon. Since the latter can be done simply with the X box at the top right of the window or by the Alt+F4 shortcut, whereas the Close (and File New, which currently does the same thing as Close) can only be done by the menu.
Of course, there really isn't any reason to do a File Close right now. Since opening a new file does close the current one.
Good comment. I'll take a look again at the icons during the Beta testing.
I agree there isn't a 'need' to have a Close button or do File Close, but if that is the case why have it on the menu at all. One example for having it in at least one location would that be some users may initially concerned that the File Add Gedcom(s) may merge and not close the currently opened file.
Actually the GEDCOM file is loaded into memory. The Add GEDCOM(s) command will actually merge the currently loaded files. The original files never get locked or changed in any way, at least until version 2.
So Behold's use of "open" and "close" is not really correct, but it is what people are used to seeing. So I'll have to weight these against each other and decide what to use.
Once editing is implementing, Behold will actually be using the GEDCOMs as its "database" for input and output, with customizations going into Behold (.bho) files.
You must login to post your reply.
Copyright © Louis Kessler
All Rights Reserved