WOW with quick question about Girder support...

[msm]

From communications with SUB I think the problem is that the GBPVR recording device is efectively working as a service, and so has issues in using the clipboard to communicate with Girder, which is how Girder processes its events. This means communications have to be sent via the Girder internet server device.

The great news is SUB has this working for the next version, and i have just finished the .gml to change channels via Girder, so keep your eyes pealed for the new version.

Matt

[dutchal]

I dont understand .. with the girder event library (basically a windows dll) you can send events to girder by calling one of the dlls functions without having to use the internet event client/server.. in what way is that related to the clipboard ?

[sub]

Behind the the scenes the event library (and .exe) use WM_COPYDATA to transfer data between processes. Basically this data goes via clipboard. This was mentioned in the Girder forums, and I've been able to confirm that this is the case. I dont know what the guy was thinking when he did that.

You can see the same problem on XP by running Girder under one desktop, then switch to another user's desktop and run the girder event.exe. Messages just dont make it there. Run them on the same desktop session as Girder and they get there fine.

[dutchal]

That was pretty helpfull cause it just rang a bell that this may be the reason why one of my plugins doesnt work .. never though of this .. thanks !

[Guest]

sub,
How did you ever overcome the issue with calling girder from within an nt service?

I've been working on some pvr stuff in C# .net and I've just bumped into the same problem. I'm shelling out and calling event.exe from within an nt service and of course the event never makes it to girder. I haven't tried using COM interop and calling the girder com object but it sounds like I would have the same issue.

Also, how did you implement naitive usb-uirt support?

A push in the right direction would be greatly appreciated.

Thanks.