Re: building an AppleScript editor app
Re: building an AppleScript editor app
- Subject: Re: building an AppleScript editor app
- From: sqwarqDev <email@hidden>
- Date: Sun, 07 Dec 2014 18:59:42 +0700
Ken, many thanks for taking the time to respond.
Yes, I'm very familiar with OSAKit framework, but only in the sense that the more I look at it the more infuriating it becomes...
> What you've shown above is just the description string of the NSAppleEventDescriptor. It's not its native content.
Acutally, its the result of
NSAppleEventDescriptor *result =[_userScript executeAndReturnError:&myError];
I've been playing with both descriptorForKeyword and descriptorAtIndex: for some time, but none of that gets me past the four-letter codes. I need to query the applications dictionary to do that as far as I can tell. I was just wondering if anyone knew how that's done other than manually trying to match the four-letter code with what's in the sdef file.
If that is the task, then I don't quite undertand what you mean here:
> That's crazy. An NSAppleEventDescriptor is already a data structure. Converting it into a string and then parsing the string into a data structure is just redundant.
I have to match the code with what's in the dictionary. How else do I do that other than turning them both into the same object (eg. NSStrings or char strings)? What am I missing?
Best
Phil
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden