home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!swrinde!news.dell.com!uudell!pensoft!usenet
- From: alex@laos (Alex D. Nghiem)
- Newsgroups: comp.sys.next.programmer
- Subject: setting a custom icon for custom documents
- Message-ID: <1992Dec21.215705.814@pencom.com>
- Date: 21 Dec 92 21:57:05 GMT
- Sender: usenet@pencom.com (Usenet Pseudo User)
- Reply-To: alex@pencom.com
- Organization: Pencom Software
- Lines: 59
-
- Hello there:
-
- I finally figured out what the problem was when I tried to set a custom
- document icon for my application. To recap: I created an application and a
- custom icon for its documents. I then installed my application in ~/Apps.
- However, if I place my application on the dock, then the Worksspace would
- recognize my application as the one which created these documents. If I removed
- my application from the dock, then the Workspace would use Edit instead. Many
- people responded that I should update the File Viewer after creating the
- document -- this may not, but that wasn't the problem here.
-
- This happened because of the LaunchPaths and an AppilcationPaths defaults
- (owned by Workspace) did not include my home directory (which is where I
- installed my application). By removing these two defaults from my defaults
- database, the Workspace looked for my application in the default directory,
- which is ~/Apps.
-
-
- Best regards,
-
-
- Alex Duong Nghiem Phone: (512) 343-1111
- Pencom Software Fax: (512) 343-9650
- 9050 Capital of TX Hwy N. Mail: alex@pencom.com
- Suite 300 Mail: co-Xist_support@pencom.com
- Austin, TX 78759 Mail: co-Xist_info@pencom.com
- USA
- ****************************
- * NeXTMail gladly accepted *
- ****************************
-
-
- Begin forwarded message:
-
- Date: Wed, 16 Dec 92 16:35:04 -0800
- To: alex@pencom.com
- From: isbell@cats.ucsc.edu (Art Isbell)
- Subject: Re: setting custom icons for custom documents
-
- Alex,
- Well, you seem to have done everything I do.
- Just to clarify, when you say you dragged the document icon into IB, you do
- mean that you dragged it into the "Document Icons and Extensions" ScrollView
- and you did type the proper file extension (with no period) below the icon,
- right?
- My Workspace has no ApplicationPaths defaults variable and Eric Scott's gdb
- script that extracts defaults variables from NeXTSTEP apps doesn't report that
- Workspace responds to such a variable, so I don't know what that means. Have
- you tried removing ApplicationPaths altogether?
- On an unrelated topic, I just spent about an hour trying to figure out why
- Terminal didn't appear to be opening a new shell Window when I was logged in as
- myself (worked fine as root). I had previously experienced an involuntary
- logout due to a Workspace error (probably due to a NetInfo problem), and the
- Terminal's WinX value became -476! Had I selected Terminal's Windows menu, I
- would have probably realized what had happened. I have had similar off-screen
- coordinates written to the defaults database when apps close due to some sort
- of error, so file that one away for the future when you "lose" a Window.
-
- Art
-