-
Notifications
You must be signed in to change notification settings - Fork 5
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
Server error with Keynote 6.3 #7
Comments
Hi Niklas, Yes, it'll be AppleScript changes in Keynote 6. I currently don't have 6.3, --Chris On 25 April 2014 10:13, Niklas Riekenbrauck notifications@github.comwrote:
--Christopher Neugebauer Jabber: chrisjrn@gmail.com -- IRC: chrisjrn on irc.freenode.net -- WWW: |
Same error with Keynote 6.2. Apparently you can look up the appropriate commands via AppleScript Editor: http://support.apple.com/kb/HT6111 In this case, you need to switch out "as Classic" for "as Keynote 09". |
Thanks, Leslie. I'll see if I can get this sorted out this evening. Keynote 6 support will --Chris On 11 June 2014 14:24, Leslie W notifications@github.com wrote:
--Christopher Neugebauer Jabber: chrisjrn@gmail.com -- IRC: chrisjrn on irc.freenode.net -- WWW: |
Also, for some reason in kpfutil.py:144, NSImage.alloc().initWithContentsOfFile_(texture.path()) is returning None(Type) as a tex object, which means that tex.size() returns AttributeError. If I just return out there aren't any other errors and the server starts up. |
PS can one get access to the Keymote app to try on Glass? :) |
Shoot me an e-mail -- chrisjrn@gmail.com -- I'll add you to the beta FYI, I've not released Keymote (or upgraded KAAS) for some time now, On 11 June 2014 16:14, Leslie W notifications@github.com wrote:
--Christopher Neugebauer Jabber: chrisjrn@gmail.com -- IRC: chrisjrn on irc.freenode.net -- WWW: |
This issue is closed; #8 is to deal with the altered textures format in Keynote 6.2, which is needed to generate build previews. |
I got a execution error with the following traceback:
Any ideas why? I'm not that python-experienced to fix it myself… Maybe it has something to do with recent API changes in Keynote?!
The text was updated successfully, but these errors were encountered: