Reply to thread

Message

<blockquote data-quote="captainspanky" data-source="post: 44280" data-attributes="member: 16988">That was what I saw.&nbsp; I was pretty much all over with trying different combinations of drivers.&nbsp; Ended up as I described. The Firefly is bizarre with the codes it sends from the buttons.&nbsp; (Hitting Info gives you the CMD_BOOKMARK, for example)&nbsp; I had to use the old InputDeviceManager profile / app to figure out exactly what each button was sending.&nbsp; I have a pretty good one set up there now.&nbsp; The only thing I can't figure out is how to get the OSD up on fullscreen video/tv.&nbsp; This is done by hitting the 'u' button (if i'm remembering correctly here at work).&nbsp; I've put it the ASCII number for that button as an ACTION_KEY_PRESSED to no effect and have tried a number of Windows that have OSD in them.&nbsp; Is there some kind of Event for toggling the OSD that I'm missing? If I can get this one done, I'll post the .xml here or wherever for folks to have a look at.</blockquote>

[QUOTE="captainspanky, post: 44280, member: 16988"] That was what I saw. I was pretty much all over with trying different combinations of drivers. Ended up as I described. The Firefly is bizarre with the codes it sends from the buttons. (Hitting Info gives you the CMD_BOOKMARK, for example) I had to use the old InputDeviceManager profile / app to figure out exactly what each button was sending. I have a pretty good one set up there now. The only thing I can't figure out is how to get the OSD up on fullscreen video/tv. This is done by hitting the 'u' button (if i'm remembering correctly here at work). I've put it the ASCII number for that button as an ACTION_KEY_PRESSED to no effect and have tried a number of Windows that have OSD in them. Is there some kind of Event for toggling the OSD that I'm missing? If I can get this one done, I'll post the .xml here or wherever for folks to have a look at. [/QUOTE]

Verification