Women in Technology

Hear us Roar



Article:
  Integrating AppleScript and Cocoa
Subject:   Adding NSAppleScriptEnabled key incorrectly
Date:   2002-02-23 10:26:29
From:   scott@nocturne.org
To properly set the NSAppleScriptEnabled key you need to set it in the target, not the Info.plist in the Products folder (which is just a view of the built product).


Go to the application target and click on the 'Application Settings' tab. This will bring up UI for setting various Info.plist settings. Unfortunately, the NSAppleScriptEnabled key doesn't custom UI for it, so you'll need to switch to the 'expert' mode (click on the toggle button in the upper right) and add the key to the table.


Now when you clean, the key will be regenerated properly.

Full Threads Oldest First

Showing messages 1 through 2 of 2.

  • tried what you said
    2002-02-26 17:34:01  psheldon [View]

    But, I think author's last applescript article had the same prescription of changing XML in a view and that did work for me, so I'm not sure you are right in what you said. More confusing is that evidentally yours worked after you did that, but mine didn't. I am clueless now.
    • Michael Beam photo tried what you said
      2002-03-19 18:37:32  Michael Beam | O'Reilly Author [View]

      They''re both right. The Application Settings information in the build target gets compiled into Info.plist, so its just a matter of you typing in the XML, or letting project builder write it. However, if you do a clean build of the target, Info.plist will be deleted and a new one created from PB's Application Settings, so its best to put any keys in there, and not by hand in Info.plist.