Possible bug in Girder driver?

Greetings!
First, the good news. I've managed to either a) learn all the codes for our home theatre equipment or b) nab the codes from CCFs and ProntoEdit. I've got "basic" control over our equipment from the PC, and I'm about to put together more complex macros that will finally allow me to setup our system so that a human being can use it.
Bravo Jon!
Now, onto the "possible" bug. When I imported a "toggle" code from one of the Pronto CCFs, the repeat setting in the USB-UIRT driver window was set to 4. This toggled the device on/off, surprise, 4 times. I wasn't able to set the repeat to 0 by using the arrows, so I set it to 0 from the keyboard, and hit test - the driver locked up, and never came back.
Bug? How would one go about NOT repeating a command, especially for toggle codes? I plan on using discrete codes wherever possible, but there are times when it's not possible to find a discrete code for a particular function. Also, when I set it to 1, it toggled on/off, so I wasn't actually able to change the state that way. Is this "correct" behaviour?
Cheers!
Jeff
First, the good news. I've managed to either a) learn all the codes for our home theatre equipment or b) nab the codes from CCFs and ProntoEdit. I've got "basic" control over our equipment from the PC, and I'm about to put together more complex macros that will finally allow me to setup our system so that a human being can use it.

Now, onto the "possible" bug. When I imported a "toggle" code from one of the Pronto CCFs, the repeat setting in the USB-UIRT driver window was set to 4. This toggled the device on/off, surprise, 4 times. I wasn't able to set the repeat to 0 by using the arrows, so I set it to 0 from the keyboard, and hit test - the driver locked up, and never came back.
Bug? How would one go about NOT repeating a command, especially for toggle codes? I plan on using discrete codes wherever possible, but there are times when it's not possible to find a discrete code for a particular function. Also, when I set it to 1, it toggled on/off, so I wasn't actually able to change the state that way. Is this "correct" behaviour?
Cheers!
Jeff