Reply to thread

Message

<blockquote data-quote="AlexPlas" data-source="post: 75933" data-attributes="member: 24336">HiI have two news for you.Bad news - AVerTV version 6 use absolutely different DLL model - and using new DLLs in same way as AVerTV 5 is not possible.Good news (possible) - I have investigated communications between QuickTV application and main AVerTV application in version 5, and can make assumption - version 6 communicate in the same way. A have created new test application based on this assumption. Before starting this application QuickTV must be started. Start my app and press few buttons on your remote. If my assumption is true you should see something like this:[CODE]AVerTV version 5 QuickTV foundWM_USER + 151, wParam: 0x00000BC2, lParam: 0x00000000WM_USER + 151, wParam: 0x00000BC1, lParam: 0x00000000WM_USER + 151, wParam: 0x00000BC6, lParam: 0x00000000[/CODE]One or more WM_USER messages per button.If assumption is wrong - most of all I will close development of this plugin.</blockquote>

[QUOTE="AlexPlas, post: 75933, member: 24336"] Hi I have two news for you. Bad news - AVerTV version 6 use absolutely different DLL model - and using new DLLs in same way as AVerTV 5 is not possible. Good news (possible) - I have investigated communications between QuickTV application and main AVerTV application in version 5, and can make assumption - version 6 communicate in the same way. A have created new test application based on this assumption. Before starting this application QuickTV must be started. Start my app and press few buttons on your remote. If my assumption is true you should see something like this: [CODE]AVerTV version 5 QuickTV found WM_USER + 151, wParam: 0x00000BC2, lParam: 0x00000000 WM_USER + 151, wParam: 0x00000BC1, lParam: 0x00000000 WM_USER + 151, wParam: 0x00000BC6, lParam: 0x00000000 [/CODE] One or more WM_USER messages per button. If assumption is wrong - most of all I will close development of this plugin. [/QUOTE]

Verification