Reply to thread

Message

<blockquote data-quote="Stéphane Lenclud" data-source="post: 1182803" data-attributes="member: 140174">Alright, alright some of those rants were probably not totally baseless, I'll give you that.HID handler was implemented for the following reasons:<ul>
<li data-xf-list-type="ul">Improved remote receiver hardware compatibility.</li>
<li data-xf-list-type="ul">Improved hardware type support: gamepads, media keyboards and virtually any HID hardware.</li>
<li data-xf-list-type="ul">Improved stability and reliability.</li>
<li data-xf-list-type="ul">Improved compatibility with future and past versions of Windows. 
</li>
<li data-xf-list-type="ul">Reduced maintenance burden. That makes to life of our small team of benevolent developers a lot easier.</li>
<li data-xf-list-type="ul">Moving forward we will support profiles and keyboard mapping through that same HID handler thus enabling full compatibility with an even larger set of hardware out-of-the-box.</li>
</ul>That's a very good point. We could have arguably kept the MCE handler indefinitely.We had various discussions within our team and decided to go forward with the withdrawal knowing it would inevitably cause a few support calls on our forums.The fact that we have not yet seen a convincing case to re-introduce the MCE handler comforts me in thinking this was the right decision.Also leaving the HID handler would have caused and has caused in MP 1.12 a few support call of its own.It's for the greater good. By spending some time helping your kind and generous MP developer team make our HID handler better and working around various issues you have given a lot to the larger community.</blockquote>

[QUOTE="Stéphane Lenclud, post: 1182803, member: 140174"] Alright, alright some of those rants were probably not totally baseless, I'll give you that. HID handler was implemented for the following reasons: [LIST] [*]Improved remote receiver hardware compatibility. [*]Improved hardware type support: gamepads, media keyboards and virtually any HID hardware. [*]Improved stability and reliability. [*]Improved compatibility with future and past versions of Windows. [*]Reduced maintenance burden. That makes to life of our small team of benevolent developers a lot easier. [*]Moving forward we will support profiles and keyboard mapping through that same HID handler thus enabling full compatibility with an even larger set of hardware out-of-the-box. [/LIST] That's a very good point. We could have arguably kept the MCE handler indefinitely. We had various discussions within our team and decided to go forward with the withdrawal knowing it would inevitably cause a few support calls on our forums. The fact that we have not yet seen a convincing case to re-introduce the MCE handler comforts me in thinking this was the right decision. Also leaving the HID handler would have caused and has caused in MP 1.12 a few support call of its own. It's for the greater good. By spending some time helping your kind and generous MP developer team make our HID handler better and working around various issues you have given a lot to the larger community. [/QUOTE]

Verification