• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bug in QXPScriptingAdditions.osax?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in QXPScriptingAdditions.osax?


  • Subject: Re: Bug in QXPScriptingAdditions.osax?
  • From: David Durkee <email@hidden>
  • Date: Sun, 17 Aug 2003 19:50:51 -0500

I got the following message from an old coworker about problems caused by Quark's scripting addition:

You're gonna love this. Pierre found a problem that shows up in C6 and is caused by QuarkXPress 6. They handle scripting by installing a scripting addition (!?!?) and it seems to **** with events it has no business ****ing with. Here's the bug report I sent to Quark:

---
When QXPScriptingAdditions.osax is installed, some applications can no longer get typeQDRectangle data out of Apple Events in its native form, when sent from a script. Calling AEGetKeyPtr(&ae, keyword, typeQDRectangle, &inType, &rect, sizeof(Rect), &inSize) returns -50. You shouldn't be screwing with events, classes, enums, or coercions that aren't yours. Further, applications don't need to install scripting additions if the application is written correctly.
---

I guess if they can't compete with Creator on the quality field, their only hope was to screw with our Apple Events and make us look bad. But at least I can work around the problem in our next release by attempting to get it as a list instead of relying on AEGetKeyPtr to do the coercion for me.


On Saturday, August 16, 2003, at 10:40 AM, Emmanuel wrote:

Hello,

jj has found that QXPScriptingAdditions.osax induces major misbehaviors of Smile (such as, hanging the machine up to the menu bar clock for minutes).
Users have reported other oddities induced in AppleScript by QXPScriptingAdditions.osax.

Since Smile is very "AppleScripty", the incompatibility with Smile is a likely sign that QXPScriptingAdditions.osax is breaking something in AppleScript.

If you script, you observe strange things and you have QXPScriptingAdditions.osax installed, I would suggest considering the possibility of un-installing it.

Emmanuel
_______________________________________________
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.


--
David Durkee
email@hidden
<http://ddurkee.homeip.net/>
_______________________________________________
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.

  • Follow-Ups:
    • Re: Bug in QXPScriptingAdditions.osax?
      • From: Emmanuel <email@hidden>
References: 
 >Bug in QXPScriptingAdditions.osax? (From: Emmanuel <email@hidden>)

  • Prev by Date: Netscape email scripting
  • Next by Date: Re: Extract Folder Name from Full Path
  • Previous by thread: Bug in QXPScriptingAdditions.osax?
  • Next by thread: Re: Bug in QXPScriptingAdditions.osax?
  • Index(es):
    • Date
    • Thread