Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix an AppleEvent warning that's cluttering up the console #1617

Merged
merged 1 commit into from Sep 23, 2013
Merged

Conversation

pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Sep 21, 2013

OK so no more pull requests... but this one's small.

Since I improved QS's AS action handling (getDirectTypes/getIndirectTypes) there's been an annoying log on every QS launch:

.scriptSuite warning for result type of command 'GetDirectTypes' in suite 'QuicksilverHandlers': 'list' is not a valid type name.

Just a typo on my part. It's fixed here.
Aside: .scriptSuite files shouldn't be used any more. Apparently we should use sdef files instead.

Important: Starting in OS X version 10.4, Cocoa applications can supply scripting information in the sdef format, described in “Preparing a Scripting Definition File.” This is the preferred format going forward.

skurfer added a commit that referenced this pull request Sep 23, 2013
Fix an AppleEvent warning that's cluttering up the console
@skurfer skurfer merged commit 8ee6c02 into master Sep 23, 2013
@skurfer skurfer deleted the ase branch Sep 23, 2013
@skurfer
Copy link
Member

skurfer commented Sep 23, 2013

Yeah, those messages were annoying. Was anything actually broken, or was it just the log message? (Trying to figure out what to say in the change log.)

@pjrobertson
Copy link
Member Author

pjrobertson commented Sep 23, 2013

Not sure, but I think just an annoying log. It's what AppleScript editor uses to validate if the syntax is correct, so as long as it compiled (which it did) it shouldn't affect anything.

On 23 Medi 2013, at 11:26, Rob McBroom notifications@github.com wrote:

Yeah, those messages were annoying. Was anything actually broken, or was it just the log message? (Trying to figure out what to say in the change log.)


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants