Xref: utzoo comp.sys.mac.misc:492 comp.sys.mac.apps:440 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!uupsi!sunic!kth.se!news From: d88-jwa@nada.kth.se (Jon W{tte) Newsgroups: comp.sys.mac.misc,comp.sys.mac.apps Subject: Re: Avoiding "Some documents could not be opened or printed".... Message-ID: <1990Jun4.094133.25114@kth.se> Date: 4 Jun 90 09:41:33 GMT References: Sender: news@kth.se (News Administrator) Reply-To: d88-jwa@nada.kth.se (Jon W{tte) Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 31 In article , jtn@ADS.COM (John Nelson) writes: > opening of documents. If I 2-click on a document, this launches the > appropriate application and all is fine with the world. Now I go back > to the finder and 2-click on another document expecting this document > to be opened also, but instead I get an alert box that says "Some > documents could not be opened or printed." > I think Lightspeed C does this although Write 4.0 does not. Is this > something that I have to modify in the system/finder or in the apps How this is implemented: When an app already is running, and you double-click another document, MF looks through the application's menus, and looks for "Open" kind of menu items (there are some defaults, and the application writer can supply appropriate suggestions for his app using special resources) MF then short-circuits the SFGetFile dialog (the "Open what file") to return the clicked document. Now, if you double-click on a project file in LSC, it won't open, because you can't have more than one project open at a time. I think Symantec made the decision that "the user'll always have a project open" so they didn't stick "Open Project" into the special resources. What's more annoying is that many developers rely on the "default" values for the menu text, and what happens when you translate the program to (for instance) swedish... right on, no auto-open :-( Jon W{tte, Stockholm, Sweden, h+@nada.kth.se