View Single Post
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#231
Originally Posted by sixwheeledbeast View Post
Eventually as the Compatible Devices List gets bigger maybe the search can be adapted to search for a device.
Actually, my original design included two different collections to choose from -- you could either choose a keyset or a device. But the device list I came up with was so pitifully small, I just gave up on it. I am indeed hoping that the Compatible Devices List grows rapidly! (And in fact I'm adding the compatible devices into Pierogi bit by bit, even though I don't yet have an interface to access them yet...)

are there any guidelines for testing keysets?
The biggest problem for Pierogi right now is that all of the keyset information I've got, every last bit of it, was derived from folks "reverse-engineering" their remote controls by pointing them at an IR receiver hooked up to a PC and pressing each button one by one. That's how the LIRC folks do it, how the Pronto folks do it, and how the JP1 guys do it. So I'm sure there are times when people wrote down the wrong timing value, or missed a button, or swapped two different buttons, or made an error naming the button, etc. (Let alone the errors I make importing the config files.) The data is not going to be perfect. What I would most like to know is this -- when people find a keyset that works with their device, do all the buttons work? Are there missing buttons? Are there buttons swapped around?

This is time consuming work, and I don't really expect people to just sit in front of their device and hit every single button in Pierogi. But I'd love to hear about it if and when a keyset does not perform as expected...
 

The Following 4 Users Say Thank You to Copernicus For This Useful Post: