Xref: utzoo comp.sys.mac.misc:10097 comp.windows.ms:10791 Newsgroups: comp.sys.mac.misc,comp.windows.ms Path: utzoo!utgpu!watserv1!daemon From: tom@mims-iris.waterloo.edu (Tom Haapanen) Subject: Re: give me solid facts: Word for Windows Message-ID: <1991Mar26.132012.26071@watserv1.waterloo.edu> Sender: daemon@watserv1.waterloo.edu Organization: University of Waterloo, WATMIMS Research Group References: <1991Mar24.025913.29727@amd.com> <1991Mar24.065427.16198@nntp-server.caltech.edu> <1991Mar26.011127.28302@amd.com> <1991Mar26.063111.3133@cs.uoregon.edu> Date: Tue, 26 Mar 1991 13:20:12 GMT Lines: 28 Anant Kartik Mithal writes: > I also feel that the desktop/icon/running application is much better > integrated in the mac [...] For example, in Windows, if you have two > icons for Word for Windows, one in the program manager, and one on the > desktop (representing a running, but iconised version of Word), and > you double click on the icon in the program manager, you get an icon > box that says: > > ---------------------------------------- > | Microsoft Word is already running | > | OK | > ---------------------------------------- > > On the mac, if you double click on the (greyed) icon for Word, you get > back to the running copy. Also, on the Mac, double clicking on a > second word doc gets you into word with the document, with Word for > Windows, you will get the error message. This is strictly a Word for Windows problem. Applications that do not support multiple active instances are supposed to check for one already running, and if one is found, activate that running copy and bring its window to the top (see Microsoft Systems Journal, Dec/90 for details). If you want to get fancier, it is quite easy to get the already-running app to open the specified file as well, by sending it the appropriate] message (assuming, of course, that you're writing the application!). [ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ] [ "i don't even know what street canada is on" -- al capone ]