Monkeybars and ruby-debug

  3 posts   Feedicon  
Replies: 2 - Last Post: December 04, 2009 15:02
by: Logan Barnett
showing 1 - 3 of 3
 
Posted: December 03, 2009 18:00 by marnen
I'm working on my first Monkeybars project. I'm an experienced Web developer, but I've done little with desktop app development, and I really appreciate how easy Monkeybars makes the whole process.

Except in debugging. I've got ruby-debug installed and working properly with JRuby. When I put a breakpoint early in the manifest file, before Swing is loaded, it works as expected (which is why I don't think this is solely a ruby-debug issue). However, when I put it elsewhere, I get the debugger prompt in the console, but it won't accept any keystroke input at all.

Behavior from RSpec is even weirder: if I turn on the --debugger option, then I see the (rdb:1) message, but execution appears to continue without waiting for input.

I tried ruby-debug-ide, but it's got serious problems with Netbeans, so I couldn't actually use it...

I'm using Mac OS X 10.6.1, Monkeybars 1.0.4, Java 6, and JRuby 1.4.0. Any ideas?
 
Posted: December 03, 2009 21:24 by marnen
I found the problem! I was using a custom Rake task which called system() to run my app from the filesystem. Apparently keyboard input wasn't getting passed through. Time to change my Rakefile. Smile
 
Posted: December 04, 2009 15:02 by Logan Barnett

I'm glad you found the problem!

For future reference, if you have an event that doesn't appear to be firing, it's typically because there's a typo or something incorrect with the name of the method. If Monkeybars can't find the listener or the component, it simply treats the method as an ordinary method, and silently rejects your attempt to register a handler.

Replies: 2 - Last Post: December 04, 2009 15:02
by: Logan Barnett
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2010, Oracle Corporation and/or its affiliates
(revision 20120518.3c65429)
 
 
Close
loading
Please Confirm
Close