I understand what you are saying, but the case of the printer not closing is because it's been passed onto another program. Jerry
"Dennis M. Kowallek" <[email protected]> wrote: >Windows Guidelines: > > "Closing a window does not necessarily mean quitting the processes > associated with the object being viewed. For example, closing a > printer's window does not cancel the printing of documents in its > queue. Quitting an application closes its windows, but closing a > window does not necessarily quit an application. Similarly, you can > use other commands in secondary windows that result in closing the > window for example, OK and Cancel. However, the effect of closing > the window with a Close command depends on the context of the > window. Avoid assuming that the Close command is the equivalent of > the Cancel command. > > If the user has made changes in a window and then clicks the Close > command, and those changes will be lost if not applied, display a > message asking whether the user wants to apply or discard the > changes or cancel the close operation. If there are no outstanding > changes or if pending changes are retained for the next time the > window is opened, remove the window." > >To me, what is written above seems to say "IT DEPENDS". So this is not a >black and white issue. The key sentence above is: > > "Avoid assuming that the Close command is the equivalent of the > Cancel command." > >My style is to code as if 'X' is a cancel. And, like the paragraph above >recommends, I ask the user what they wish to do if canceling will cause >loss of data. But that may not be another programmer's cup-of-tea. > >-- > >Dennis Kowallek (LTools) >http://zippersoftware.com/ltools/index.htm >http://groups.yahoo.com/group/ltools > >NOTE TO LUG USERS: Use plain text if you want me to read your post. > >*** > >On Fri, 22 Jul 2011 13:40:30 +0100, "Ron Ferguson" ><[email protected]> wrote: > >>Bob, >> >>Have you considered that when saving to an Access DB this is done on the >>fly, that is when you make a change it is saved at the time you make the >>change. This is not the same as saving an image or text to file. >> >>Ron Ferguson >>http://www.fergys.co.uk/ >> >>-----Original Message----- >>From: Bob Vary >>Sent: Friday, July 22, 2011 1:15 PM >>To: [email protected] >>Subject: RE: [LegacyUG] Using "x" to exit/cancel - bug? >> >>With all due respect, you're mistaken. The Windows standard is to exit >>without saving when the "x" is clicked. Clicking "Apply" saves any changes >>without exiting the dialog and clicking "Save" saves the data and exits. >>Legacy also doesn't always make standard use of the "Apply" button, although >>I can't remember off-hand which dialog gave me trouble and don't have time >>at the moment to research it. >> >>Bob > > >Legacy User Group guidelines: >http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages after Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Archived messages from old mail server - before Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Online technical support: http://www.LegacyFamilyTree.com/Help.asp >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >our blog (http://news.LegacyFamilyTree.com). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
