Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


Don't forget to read Tuesday's email newsletter for your chance to win a free copy of Construct 2!


#Actualunbird

Posted 31 March 2013 - 12:27 PM

Interactive applications like GUIs are hard to debug with an integrated debugger: a simple breakpoint disturbs a GUIs control flow and can trigger events which without debugger wouldn't occur. I don't know about eclipse, but what I did when I programmed GUIs was dumping relevant info right in the GUI (label, textbox): Internal states, event trigger counts etc.

 

If all fails, there's always log-files. The latter has the advantage that you can detect race conditions (what did occur after what?).


#1unbird

Posted 31 March 2013 - 12:22 PM

Interactive applications like GUIs are hard to debug with an integrated debugger: a simple breakpoint disturbs a GUIs control flow and can trigger events which without debugger wouldn't occur. I don't know about eclipse, but what I did when I programmed GUIs was dumping relevant info right in the GUI (label, textbox): Internal states, event trigger counts etc. If all fails, there's always log-files.


PARTNERS