Reply to thread

Message

<blockquote data-quote="belcom" data-source="post: 523597" data-attributes="member: 89055">Ok... once again...Every new iMON HID offers 3 &quot;internal&quot; devices to windows.- (VID_15C2&amp;PID_0038&amp;MI_00&amp;Col01) Mouse- (VID_15C2&amp;PID_0038&amp;MI_00&amp;Col02) Keyboard- (VID_15C2&amp;PID_0038&amp;MI_01) RemoteMouse and Keyboard are &quot;known&quot; by Windows and so Windows accesses and processes them.Applications can also access Mouse and Keyboard directly, but not &quot;exclusive&quot;, what means that key presses or mouse movements will always also be processed by Windows in its standard way.So, if you enable keyboard in IRSS iMON plugin, MP will recieve this single key press twice, one time from Windows itself and a second time over IRSS (you can remember the &quot;double-click&quot;-'bug'?).Same thing belongs to mouse. As mouse commands are never sent to MP but to Windows, every mouse movement will happen with double speed, and every click also turns into double-clicks, because Windows get the command once from itself and a second time from IRSS.This leads us to the knowledge, that we have to uncheck &quot;Enable Keyboard Input&quot; and &quot;Enable Mouse Input&quot; to avoid any double-click issues.Next thing, if somebody wonders how the &quot;remote&quot; device works, here it is:First, over this device all commands are send to iMON (i.e. which remote should it listen to - PAD or MCE?, Keypad or Mouse mode?, and everything you see on the display)Second, all button presses which aren't sent over mouse or keyboard device come from it. These are all the media buttons, special buttons and PAD movements in Keypad mode.Now we learned, why the &quot;KeyPad sensitivity&quot; slider still works, even if &quot;Enable keyboard input&quot; is not checked.Why don't we simply delete all &quot;unneccessary&quot; checkboxes?Because there are so called DOS devices out there, and those (mostly) need these checkboxes enabled.Also, there are a few HIDs out there, which have something simmilar like old DOS firmware... strange thing, but thats why we cannot simply disable the checkboxes if a HID is detected.But we are thinking a lot about this, maybe someday we will get an idea how to get around this problem.For all HID users I attached some screenshots. Always start with the shown configuration. Only if keyboard or mouse doesn't already work try to enable them - step by step.Hope this helps a bit...Yours, belcom.</blockquote>

[QUOTE="belcom, post: 523597, member: 89055"] Ok... once again... Every new iMON HID offers 3 "internal" devices to windows. - (VID_15C2&PID_0038&MI_00&Col01) Mouse - (VID_15C2&PID_0038&MI_00&Col02) Keyboard - (VID_15C2&PID_0038&MI_01) Remote Mouse and Keyboard are "known" by Windows and so Windows accesses and processes them. Applications can also access Mouse and Keyboard directly, but not "exclusive", what means that key presses or mouse movements will always also be processed by Windows in its standard way. So, if you enable keyboard in IRSS iMON plugin, MP will recieve this single key press twice, one time from Windows itself and a second time over IRSS (you can remember the "double-click"-'bug'?). Same thing belongs to mouse. As mouse commands are never sent to MP but to Windows, every mouse movement will happen with double speed, and every click also turns into double-clicks, because Windows get the command once from itself and a second time from IRSS. This leads us to the knowledge, that we have to uncheck "Enable Keyboard Input" and "Enable Mouse Input" to avoid any double-click issues. Next thing, if somebody wonders how the "remote" device works, here it is: First, over this device all commands are send to iMON (i.e. which remote should it listen to - PAD or MCE?, Keypad or Mouse mode?, and everything you see on the display) Second, all button presses which aren't sent over mouse or keyboard device come from it. These are all the media buttons, special buttons and PAD movements in Keypad mode. Now we learned, why the "KeyPad sensitivity" slider still works, even if "Enable keyboard input" is not checked. Why don't we simply delete all "unneccessary" checkboxes? Because there are so called DOS devices out there, and those (mostly) need these checkboxes enabled. Also, there are a few HIDs out there, which have something simmilar like old DOS firmware... strange thing, but thats why we cannot simply disable the checkboxes if a HID is detected. But we are thinking a lot about this, maybe someday we will get an idea how to get around this problem. For all HID users I attached some screenshots. Always start with the shown configuration. Only if keyboard or mouse doesn't already work try to enable them - step by step. Hope this helps a bit... Yours, belcom. [/QUOTE]

Verification