Version 0.9.7 Bugs
The highlighted comment was created in this revision.
2 bugs so far that I have found:
1) A left over java process seems to hang around for each full execution of RoboRunner. This needs to be tracked down and eliminated (could it be the callback queue in RoboRunner?)
2) When RoboRunner throws an error (for example, due to a missing robot), RoboJogger does not realize that RoboRunner has died and the controls to "stop" RoboRunner do not function. This results in RoboJogger being stuck and requiring a force quit. This should be fixed so that either RoboJogger correctly detects the failed start of RoboRunner or at least is able to reset everything if the command is given to stop RoboRunner.
Are these bugs present in 0.9.6? I'm finding it quite annoying to have to keep restarting robojogger =)
