home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!usenet.ins.cwru.edu!agate!stanford.edu!morrow.stanford.edu!morrow.stanford.edu!usenet
- From: Christopher_Lane@Med.Stanford.EDU
- Newsgroups: comp.sys.next.misc
- Subject: Re: Silly NeXT question from user who should know the answer
- Date: 28 Jan 1993 18:02:01 GMT
- Organization: Stanford University
- Lines: 20
- Message-ID: <1k972pINNi0i@morrow.stanford.edu>
- References: <1993Jan28.133046.15696@cubetech.com>
- Reply-To: Christopher_Lane@Med.Stanford.EDU
- NNTP-Posting-Host: ssrg-next-1.stanford.edu
-
- In article <1993Jan26.232845.12294@cs.yale.edu> nathan@laplace.biology.yale.edu
- writes:
- > How can a user "inform" the FileViewer that files with certain
- > extensions should have a corresponding app selected as the default
- > launch app? It's easy enough to select an app already displayed in the
- > Tools panel of the inspector, but how does one add a new choice? Dragging
- > an icon into that area doesn't seem to work (it should!)...
-
- This is partially what the old 'Unknown' application does, though I've not
- posted a 3.0 version of it since it's original function keeps getting reduced
- as NeXT fixes/changes things. It basically is a remapping app that assigns
- icons and owners to file types that don't have them don't have the right ones.
-
- Unfortunately, Unknown or any of the various 'edit the iconheader' suggestions
- are not guaranteed to work as it also depends on how the target application is
- implemented. It has to both accept files with the appropriate method and not
- be overly picky about filtering out extensions it doesn't recognize. (Some
- do reject based on extension even though the content might have been OK.)
-
- - Christopher
-