MissileUI

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

Score 50.0%

Description:

Front-end for the USB Launcher program hosted on http://sourceforge.net/projects/usblauncher/, which controls the M&S and Dream Cheeky USB Missile Launchers.
As opposed to my Kommander script of last year, this is a stand-alone application with much better functionality. E.g., it will now find the location of ctlmissile on its own; holding down the mouse button on a directional arrow will make the missile launcher continue to move smoothly in that direction until the button is released.

Last changelog:

12 years ago

Version 1.1: The program now saves the settings file in the user's home directory, rather than wherever you happen to launch the program.

zelmo
12 years ago

Not that you'd ever guess it :P but this was my first-ever Qt program, which I built after reading just two or three chapters of Blanchette and Summerfield's book. Needless to say, I still knew next to nothing about Qt at that point.

Since then, I've read more of the book and also gotten my hands on Qt-Assistant, and have been building another Qt project using the newfound knowledge (see StreamMinder from the link to "Other content from Zelmo").

Normally I'd just let this project stand as it is, since it's basically functional. But I noticed recently that someone has developed a kernel module for the Dream Cheeky missile launcher, which gives much finer control than the command-line program currently being used as a back-end for MissileUI. So once I get to a resting point on StreamMinder, I'm going to come back to this project and re-do it from the ground up, using the new kernel module as a back-end.

In the meantime, I'd like to hear two things from current users:
1. Is there anything missing from the UI?
2. In your experimentation with the command-line client, exactly how many seconds does it take to to fire one missile? (I currently have it clocked at 4.45 seconds, but that seems to be inaccurate by a matter of milliseconds.)

Report