So does keymando work with Mountain Lion?

Showing 1-7 of 7 messages
So does keymando work with Mountain Lion? David Luebke 8/13/12 7:40 AM
When I launch KM nothing appears to happen. Doesn't enter the application and doesn't appear in the clover-tab list of open apps. Only thing I could figure out is that I'm running Mountain Lion on a new MBP, and can't find anything on the web that explicitly says the new OS is supported. Thoughts? 

Thanks, Dave
Re: So does keymando work with Mountain Lion? David Luebke 8/13/12 7:46 AM
By the way, I should have mentioned that this is the latest version of Keymando (1.2.2) just downloaded from the "try for free" link, and that I did go through the process described in another post:

After some debugging with Kevin and JP, I found the issue. Keymando is 
failing to create its keymandorc.rb file if it doesn't exist when it 
launches and terminating immediately. It is unclear whether this is a 
Lion 10.7.4 related problem or a bug in the latest version. You can 
fix it by opening up a terminal and typing: 

touch ~/Library/Application\ Support/Keymando/keymandorc.rb 

Keymando will then launch successfully and you can edit keymandorc.rb 
to add your customization. 

The ~/Library/Application\ Support/Keymando directory did not exist, so I created it with mkdir and then touched the .rb file as described above, but Keymando still exits on launch. 

Dave
Re: So does keymando work with Mountain Lion? Chris Dekter 8/16/12 4:18 AM
I've tried it out on two different MacBooks both running ML and had no problems (only tested basic functionality so far). Certainly no issues on startup like you are seeing.

-- Chris
Re: So does keymando work with Mountain Lion? Chris Dekter 8/16/12 5:02 PM
I jinxed myself - now it doesn't work on my work MacBook. It's crashing on startup:

Process:         Keymando [419]
Path:            /Applications/Keymando.app/Contents/MacOS/Keymando
Identifier:      com.keymando.keymando
Version:         1.2.2 (1.2.2)
Code Type:       X86-64 (Native)
Parent Process:  launchd [129]
User ID:         501

Date/Time:       2012-08-17 09:59:42.818 +1000
OS Version:      Mac OS X 10.8 (12A269)
Report Version:  10

Crashed Thread:  0

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @executable_path/../Frameworks/Growl.framework/Versions/A/Growl
  Referenced from: /Applications/Keymando.app/Contents/MacOS/Keymando
  Reason: image not found

Binary Images:
       0x100000000 -        0x100003fff +com.keymando.keymando (1.2.2 - 1.2.2) <30800418-17AD-3AC6-8DAE-29A495F831D8> /Applications/Keymando.app/Contents/MacOS/Keymando
       0x10000a000 -        0x100c24fa7 +libmacruby.1.9.2.dylib (0.10) <5425D62F-FC4F-3CB5-AD85-89B571FA6214> /Applications/Keymando.app/Contents/Frameworks/MacRuby.framework/Versions/0.10/usr/lib/libmacruby.1.9.2.dylib
       0x100cba000 -        0x100cd1fff +org.andymatuschak.Sparkle (1.5 Beta 6 - 313) <7D298003-0E13-7E27-8237-9C0E1D621133> /Applications/Keymando.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle
    0x7fff6d16a000 -     0x7fff6d19e93f  dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
    0x7fff902f1000 -     0x7fff902f1fff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff9065b000 -     0x7fff9075dfff  libcrypto.0.9.8.dylib (47) <74F165AD-4572-3B26-B0E2-A97477FE59D0> /usr/lib/libcrypto.0.9.8.dylib
    0x7fff95415000 -     0x7fff95771ff7  com.apple.Foundation (6.8 - 945) <0C972F73-0C07-3384-98F2-B176E0289494> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff960e6000 -     0x7fff96d10fff  com.apple.AppKit (6.8 - 1187) <C9309F5C-9441-3E5B-A120-B03FEDDA63F9> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff9754d000 -     0x7fff9754dfff  com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff977f3000 -     0x7fff977f3fff  com.apple.Carbon (154 - 155) <372716D2-6FA1-3611-8501-3DD1D4A6E8C8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon

 
Re: So does keymando work with Mountain Lion? David Luebke 8/19/12 9:13 PM
So...maybe an issue with Growl? 

Anybody out there got advice, or ideas for how I can debug this? I'm new to MacOS so don't know where to get logs like the below, but if you tell me where to look I can try to post information here. 

I'd love to use Keymando if I can make it work...

Dave
Re: So does keymando work with Mountain Lion? David Luebke 8/28/12 2:01 PM
Thanks to Kevin who helped me figure this out. We tried several things, so it might have been a combination of bugs, but thing that made it work seemed to be to ensure the "Enable access for assistive devices" option was checked under System Preferences -> Accessibility. 
Re: So does keymando work with Mountain Lion? Kevin Colyar 8/30/12 9:03 PM
This issue have been fixed in the latest update 1.2.3--
Kevin Colyar