Reply to thread

Message: <blockquote data-quote="CyberSimian" data-source="post: 1161027" data-attributes="member: 141969">I have now completed it. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up    (y)" loading="lazy" data-shortname="(y)" />  Every button on the Ortek/Hama remote can be trapped by the AutoHotKey script and mapped to some other keystroke. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />  The problem is that this is only about 75% of the solution. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown    :(" loading="lazy" data-shortname=":(" />The Ortek/Hama has 48 buttons (excluding the mouse direction pad), but three of those buttons duplicate three of the other buttons, so the Ortek/Hama sends only 45 different codes (two of which are left-mouse button and right-mouse button).About 30 of the buttons have their conventional meanings.  Some of these buttons are supported directly by MP, others buttons can be mapped using AutoHotKey plus the MP keyboard shortcuts. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />  The problem is with the remaining buttons, which have names such as: My TV, My Music, My Pictures, My Videos, Recorded TV, Live TV, Guide.  These buttons all imply a transfer to a different panel in MP, but there are no keyboard shortcuts to perform this transfer. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite16" alt=":cry:" title="Crying    :cry:" loading="lazy" data-shortname=":cry:" />For MP1, there is the "Generic Keyboard Input" plug-in.  If it still works with MP 1.12, it provides a lot of capability (possibly making the AutoHotKey script redundant <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek!    :eek:" loading="lazy" data-shortname=":eek:" />).For MP2, there is...? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused    :confused:" loading="lazy" data-shortname=":confused:" />But the conclusion is that AutoHotKey does not provide a full solution for either MP1 or MP2.  So some different solution will need to be developed for MP2.-- from CyberSimian in the UK</blockquote>

Verification