Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1167680" data-attributes="member: 82144">You're right. It had been too long since I looked at my code. I should have said usage-page/usage. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite11" alt=":rolleyes:" title="Roll Eyes&nbsp; &nbsp; :rolleyes:" loading="lazy" data-shortname=":rolleyes:" />So I mean (example): can one window register to receive the general desktop page while another registers to receive the keyboard/kepad page? ...or what about different windows registering for different usage ranges on the same usage page?Ha, I don't blame you. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Note that Hauppauge remotes are already supported using the first method, so it isn't as over the top as you might think. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />My comment was to point out that the definition of &quot;you&quot; and &quot;your&quot; appears to be limited to one window. As it says in the doc, you must provide the window handle:So my understanding is that only that single registered window would receive the desired WM_INPUT messages for the given usage-page + usage range combination. In the context of this discussion, the implication is that the MP HID handler's window will be the only window that receives messages (regardless of background/focus status).Further, the limitation to one window receiving messages still applies overall when registration is done without RIDEV_INPUTSINK. However, the actual receiving window changes depending on which window has focus. If your receiver window never has focus then I'd expect it never receives any raw input WM_INPUT messages.</blockquote>

[QUOTE="mm1352000, post: 1167680, member: 82144"] You're right. It had been too long since I looked at my code. I should have said usage-page/usage. :oops::rolleyes: So I mean (example): can one window register to receive the general desktop page while another registers to receive the keyboard/kepad page? ...or what about different windows registering for different usage ranges on the same usage page? Ha, I don't blame you. :) Note that Hauppauge remotes are already supported using the first method, so it isn't as over the top as you might think. ;) My comment was to point out that the definition of "you" and "your" appears to be limited to one window. As it says in the doc, you [B]must [/B]provide the window handle: So my understanding is that [I]only that single registered window[/I] would receive the desired WM_INPUT messages for the given usage-page + usage range combination. In the context of this discussion, the implication is that the MP HID handler's window will be the only window that receives messages (regardless of background/focus status). Further, the limitation to one window receiving messages still applies overall when registration is done without RIDEV_INPUTSINK. However, the actual receiving window changes depending on which window has focus. If your receiver window never has focus then I'd expect it never receives any raw input WM_INPUT messages. [/QUOTE]

Verification