home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!spool.mu.edu!enterpoop.mit.edu!eru.mt.luth.se!kth.se!dront.nada.kth.se!d88-jwa
- From: d88-jwa@dront.nada.kth.se (Jon Wtte)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: SFGetFile's directory after an Open Event
- Message-ID: <1993Jan4.205533.25405@kth.se>
- Date: 4 Jan 93 20:55:33 GMT
- References: <1993Jan4.190815.5881@ccu1.aukuni.ac.nz>
- Sender: usenet@kth.se (Usenet)
- Organization: Royal Institute of Technology, Stockholm, Sweden
- Lines: 24
- Nntp-Posting-Host: dront.nada.kth.se
-
- In <1993Jan4.190815.5881@ccu1.aukuni.ac.nz> russells@ccu1.aukuni.ac.nz (Russell Street) writes:
-
- >After an application receives an 'odoc' Apple Event to open a document
- >should it arrange it so the next Standard File [Open] Dialog that is
- >brought up by the user is the same directory that the 'odoc' document
- >came from?
-
- If Apple thought that would be the right thing to do, they would
- have done it themselves. Doing so requires changing lo-mem globals;
- that's a dangerous habit you should break out of.
-
- Not to mention: if the app gets an odoc, the user most probably has
- the folder open in the Finder, and going there and double-clicking
- would be much easier than choosing "Open" in the File menu.
-
- Cheers,
-
- / h+
-
- --
- -- Jon W{tte, h+@nada.kth.se, Mac Hacker Deluxe --
-
- Speed is arbitrary. Don't believe me? Try a PowerBook 180 running
- System 7 against a 486 laptop running Windows 3.1.
-