BleepBloop

[reven]

also i dont think the colour buttons work (rewind works fine, which has the same mapping as red, but blue/yellow/green dont work).

[KingArgyle]

Yep, you are correct. Should be fixed now. I uploaded the corrected version to the wiki.

[reven]

you're missing one more aswell
Power = {f12}

and {f7} doesnt appear to be working for me.

[KingArgyle]

Thanks to Reven's testing, version 1.03 is now available. I believe this should be the last change for a while.

Version 1.03:
* Fixed issue with missing Yellow, Blue, Green Button mapping
* Added mappings: PgUp = prior.wav, PgDn = next.wav
* Added mappings: Power = power.wav

Version 1.03 is on the wiki.

[sleptoor]

As we discussed in the "wishlist" section, BleepBloop is not audible when the GBPVR is not focused. I didn't do a thorough test though so I'll make sure when I get home from work - but that was my experience last night - all I did to fix the issue was hit the green button which bring focus to the app.....

Love the plugin so far though, good work!

[KingArgyle]

What remote are you using? The plugin is expecting keyboard events to be sent to GBPVR, and right now it monitors any keyboard event that the application tosses. If another application such as Girder is sending the keystrokes to GBPVR then it might now catch those keystrokes, and I would have to figure out how to capture these commands.

What I might do is put in some logging information to log out the various WM_messages that that the plugin detects, and see if I can track it that way.
As I don't have a remote on my development machine, and the StreamZap remote I use on my HTPC machine, only sends the commands when GBPVR has focus it may be a little difficult for me test.

[sleptoor]

I have the 45 button grey Hauppauge (with a PVR350). Recently I used the info from one star (this thread) to add the non-focused ability to my remote. Again, I'll do some testing tonight and I can be your guinee pig as to testing new versions of the plugin if you want.

[KingArgyle]

Thanks for the links. I'll see what I can do.

Are you still using the FindMessage and Sendmessage items to send the keyboard events to GBPVR as discussed in this thread?:


http://forums.nextpvr.com/showthread.php...ge=1&pp=10

[KingArgyle]

Sleptoor, if you don't mind playing around with the ini file for your remote you might be able to get it to respond to the commands by sending the WM_KEYFIRST/WM_KEYDOWN message.

The plugin looks for the WM_KEYDOWN message to be sent to the windows message queue so and intercepts it before it gets there, processes the command, and then allows the message to be passed onto the queue so that other plugins and GBPVR functions can process there messages correctly.

I found this thread on the sageTV forum, that was actually pretty interesting:

http://forums.sage.tv/forums/showthread.php?t=4277

The ZIP contains a good write up of the various commands the Hauppauge remote ini will accept. I'd try messing around with the fgnwnd() and SendMsg() functions, WM_KEYDOWN/WM_KEYFIRST maps to hex 100 or dec 256.

[sleptoor]

KingArgyle, I just did a thorough test and yes the sounds do not work when the window is not focused but everything else works perfectly. I'm a bit of a feeb with the ini. I'm just starting to understand what its doing and how to manipulate it.

my original - OK={findwnd(,GB-PVR)}{SendMsg(32771,229,0)}

I tried these.

OK={findwnd(,GB-PVR)}{SendMsg(WM_KEYDOWN,229,0)} - did not work, no results at all

OK={findwnd(,GB-PVR)}{fgnwnd()}{enter} - brings focus to the Application thereby giving it sound but defeats the benefit of being able to use the PVR and the computer at the same time

So how should the syntax look?

Dana