Quote:
|
Originally Posted by Leav
exactly the most annoying part! plus, if you press stop twice, it will crash.
|
I think this is one of those times where an open source advocate somewhere mutters "Well, you've got the
source..."
Seriously, though, if the double-press issue (or any other GUI glitch) is giving you a hassle, it shouldn't be too hard to fix. As a hack, you could probably throw a little finite state machine into the GUI interface software that either hides or ignores the stop button if the system is not in a state where stopping makes sense.
As a student at CMU, I wish I could say "That bug shouldn't be there," but I've worked on too many projects like this to say that with a straight face
. Not having been involved with the CMUCam project, my guess would be that it sounds like the hardware people assumed the software people wouldn't do something "obviously incorrect," and the software people assumed the hardware people wouldn't allow the camera to choke on "meaningless but well-formed input." Control system design teams, take note: there's a lesson here...
As for me personally, given that the CMU cam is pretty awesome, and has the distinct advantage over other solutions of existing
right now, I'm willing to forgive the design team for missing the "totally awesome" mark. If anyone decides to tidy up the software, share the fixes with the rest of us!
Best of luck to everyone,
Mark