Well I called it a spoiler, because it removes any need to put a build environment in place, in case you wanted to build more modules for other items in your system. But if you do not need to build anything else, then you cut right to the chase.
It's kind of like a movie. If you want to follow the plot, and experience all the characters in it, you watch the whole thing. Could turn out great, could be 2hrs of your life you'll never get back. But if you don't want to sit through the whole thing, you can easily view a "spoiler" somewhere, and cut right to the end.
Kind of like LMCE. If you want to learn how things work in the system, and gain experience and knowledge in the process. Start from the beginning, and build your own module.
If you want to be lazy, not learn anything, and just "get it working" , use the "Spoiler" . And if you would have read the entire wiki entry, this would have become clear.
I apologize for your confusion, but at least now, if you need to build another module to make something else work in your system, the work has been done, and it should be a piece of cake.
But so as not to seem a hardass, I will edit the wiki to say "The Spoiler: Instant Fix!"
Bet wishes and Regards,
Seth
I guess I wouldn't have minded so much if it would have worked. Sorry for the somewhat short post, I was a little frustrated at the seemingly endless failures, at getting the usb-uirt to work.
Now funny thing, that is fixed, but whenever I go and click or use the keyboard on the screen orbit, my tv shuts off! LOL. This only happens the first time after a dcrouter refresh, the rest of the actions do not send the code. hmmmmm. The remote I was using the most to train when troubleshooting the code sending issue was the tv power button. Maybe all my failed attempts before at getting it to work buffered up and it's relieving itself now.
But seriously, what would cause that? I have looked in the home page under orbiters, interfaces etc, I see nothing that could cause this. Now it's working too well!