4 Matching Annotations
  1. Last 7 days
  2. Sep 2019
  3. May 2017
    1. Calling from Python As of 10.10, AppleScript can use Cocoa frameworks in any Script Editor-based script. This makes it easy for Python and other languages that have Objective-C bridges to call AppleScript directly, without having to package everything as an Xcode app. Stick one or more compiled .scpt files containing AppleScript-ObjC "classes" into a folder, e.g.: use framework "Foundation" use scripting additions script MyASClass property parent : class "NSObject" -- on test() activate display dialog "Hello from AppleScript!" end test end script then just use it from Python like this: from Foundation import NSBundle, NSClassFromString import AppleScriptObjC NSBundle.alloc().initWithPath_(FOLDERPATH).loadAppleScriptObjectiveCScripts() MyASClass = NSClassFromString(u"MyASClass") # get the ASOC class... MyASClass.alloc().init().test() # ...then instantiate and call it

      Given that appscript is deprecated, I'm looking at how to call AppleScript directly from Python. This section is a "hello world" demonstration of how.

  4. Jan 2015
    1. Bluetooth—so simple and yet so troublesome. For a subsection of users, Yosemite is causing problems with Bluetooth accessories and connectivity. One solution proffered by iDigitalTimes is to disconnect all USB preferences, shut the Mac off for several minutes and then try again from the beginning. You may have to teach Yosemite about your Bluetooth accessories afresh instead of relying on what Mavericks has passed on. Over on the official Apple forums, it looks like resetting your machine's PRAM (Parameter Random Access Memory) once or twice might fix the problem. PRAM is where all of the core information about your system is stored, and you reset it by booting up, then holding down the Cmd+Option+P+R keys right after you've hit the power button. When you hear the startup sound for the second time, you can let go.

      I may need to try this solution.