Re: Forcing 'tell app' to use carbon, rather than classic app
Re: Forcing 'tell app' to use carbon, rather than classic app
- Subject: Re: Forcing 'tell app' to use carbon, rather than classic app
- From: email@hidden
- Date: Tue, 7 Jan 2003 15:01:08 -0500
Bill-
Just taking a quick glance at this, the difference in the Classic versus
non-classic version of the same app seems to be its "kind". You may try
choosing the preferred app by knowing this. A Classic app has the kind
designation of "Classic Application" and a non-classic app has a kind of
simply "Application". I'm not sure about a carbonized app's designation.
-Cassj
Bill Bug <email@hidden>
Sent by: email@hidden
01/07/03 10:31 AM
To: email@hidden
cc:
Subject: Forcing 'tell app' to use carbon, rather than
classic app
Hi All,
I'm sure this is a lot easier to do than it seems.
Here's what I'm trying to do.
I have a complex AS application I'm porting from OS 9 to OS X 10.2.3.
In addition to giving it a nice Cocoa front-end, I'm now able to do a
lot of what I was doing with Scripting Additions using the handy-dandy
'do shell script' command and the wealth of Unix tools at my disposal.
The problem I'm running into is this.
The machine where I'm developing - and ultimately running - this AS App
has both Classic & OS X versions of some of the apps being driven via
AppleScript. For instance, I've got both the classic & - I assume -
carbonized versions of FileMaker Pro 5.5. I need to now have the 'tell
application' directive link to the carbonized FMP, as opposed to the
classic version, and I'm not sure how to direct the AS compiler in AS
Studio/PB to do that.
I tried the naive trick of simply changing the old FMP's name to
'FileMaker Pro for Classic'. All that did was change the references in
my AS code to 'tell application "FileMaker Pro for Classic"'. When I
tried to manually change these references to 'tell application
"FileMaker Pro"', so as to force the AS compiler to bind to the proper
version of the FMP, the AS compiler simply forced the references back
to 'tell application "FileMaker Pro for Classic"'.
I remember learning awhile ago how this binding is created, and I
vaguely remember under OS 9 it was based on the app file's type or
creator. I assume it's a bit different under OS X.
Can anyone offer a fix for this problem.
Thanks ahead of time for your help.
Cheers,
Bill Bug
Bill Bug
Senior Analyst/Ontological Engineer
Computer Vision Laboratory for Vertebrate Brain Mapping
Department of Neurobiology & Anatomy
Drexel University College of Medicine
2900 Queen Lane
Philadelphia, PA 19129
215 991 8430 (ph)
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.