Hello all, I've delivered an application, (Mac OS X 10.4, LWM 4.4.5 Pro) and I'm noticing that when it's open, and Lispworks is not, double clicking a lisp file (in this case, a .lisp extension) brings the delivered application to the foreground. I'm not writing a LISP editor or anything like it, so this is really sort of a problem for me. Any thoughts? -- ===================== Joshua Taylor tayloj@rpi.edu
On Aug 18, 2005, at 13:54, Joshua Taylor wrote: > Hello all, > > I've delivered an application, (Mac OS X 10.4, LWM 4.4.5 Pro) and > I'm noticing that when it's open, and Lispworks is not, double > clicking a > lisp file (in this case, a .lisp extension) brings the delivered > application > to the foreground. I'm not writing a LISP editor or anything like > it, so this > is really sort of a problem for me. It sounds like one of your CFBundleTypeExtensions is set to .lisp ... CFBundleTypeExtensions is a child of CFBundleDocumentTypes in your bundle's Info.plist I hope this helps, Shawn -- Shawn MacIntyre Edmonton, Alberta, Canada
Ah, that does provide an easy way to fix it. Thanks! On 18/08/05, Shawn MacIntyre <smacintyre@mac.com> wrote: > > On Aug 18, 2005, at 13:54, Joshua Taylor wrote: > > > Hello all, > > > > I've delivered an application, (Mac OS X 10.4, LWM 4.4.5 Pro) and > > I'm noticing that when it's open, and Lispworks is not, double > > clicking a > > lisp file (in this case, a .lisp extension) brings the delivered > > application > > to the foreground. I'm not writing a LISP editor or anything like > > it, so this > > is really sort of a problem for me. > > It sounds like one of your CFBundleTypeExtensions is set to .lisp ... > > CFBundleTypeExtensions is a child of CFBundleDocumentTypes in your > bundle's Info.plist > > I hope this helps, > Shawn > > -- > Shawn MacIntyre Edmonton, Alberta, > Canada > > -- ===================== Joshua Taylor tayloj@rpi.edu