On Dec 22, 2006, at 17:45 UTC, John McKernon wrote: > >The virtual file system > > supports four-byte type codes (accessed via f.MacType), but does not > > support creator codes." > > Does this mean that if a Mac user double-clicks on a virtual > volume, that the appropriate application won't open and read > it (since there's no creator code)?
No, it means that if a Mac user could double-click on a virtual file within a virtual volume, the appropriate application wouldn't open. But of course they can't do that; the Mac knows nothing about these virtual files. The virtual volume itself is a Mac file (if it's on a Mac), and supports creator codes like any other Mac file. > Ditto for getting an appropriate icon (which is usually assigned via > the application's plist)? Ditto again. The Finder can't display virtual files, so there would be no way for any icons to be shown anyway. > I'm assuming that a virtual volume doesn't become "mounted" > like a real volume does, that it's simply a handy kind of file > that RB opens like most folder items except that it can have > virtual files and folders contained within it (accessible using > Child), but it appears to the user as a regular single file. Right. That's why your questions above, about how the Finder sees virtual files, are off base -- it doesn't see them at all. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
