Reply to thread

I understand the frustration.



As I said, you are free to keep the old skin. We should have noted this more explicitely in the release news.

[USER=54906]@catavolt[/USER] , could you please amend the release news accordingly if you have a minute?



The change is very technical and invisible. Actually the HID handling is much more logical but I certainly understand that you challenge the need for it. AFAIK the HP transceivers are perfect eHome devices, however, I a m not at all familiar with the blaster side of MePo and hence won' make any judgement here.



It would not be very difficult to redefine correct settings in the config. I have to confess that we did discuss (many months ago) about any automated import of existing MCE mappings on to the Generic HID definitions, but it got lost in the process. We'll take up the subject again to see if we can either provide an automatic import or at least a more detailed explanation of how to migrate existing customizations to the HID side..


It is understandable that you "like to stay with stuff that works". In that case you may want to apply caution before upgrading a system that is acting to your needs.



That may be true for some devs but definitely not for everybody. In this specific case Stephane has upgraded the remote handling to be fully Microsoft-compliant. It solves a lot of other issues and the only - yet unpleasant - thing needed, is to possibly redefine the different keys in the remote settings. IN my specific case I have never changed the standard MCE settings of MePo, therefore I did not even noted any change.


Top Bottom