gfb107 wrote:In many cases RMIR isn't hiding stuff, it's just managing it differently and exposing it in different places.
Two examples come to mind:
- Protocol upgrades. RMIR automatically ensures that the required protocol upgrade gets loaded, and doesn't show those protocol upgrades in the Protocols tab.
- Keymoves. RMIR keeps keymoves associated with a device upgrade as part of the device upgrade, and doesn't show them in the keymoves tab.
In both cases, stuff is being managed differently than IR, and appear hidden. But both can be seen by looking at the individual device upgrades, specifically on the Output tab.
I understand what you're saying, but you need to listen to what we're saying too if you want to make this the best tool it can be. For a non-expert I agree that it's a good idea to keep things simple by hiding stuff, and you are hiding stuff - let's be honest. For example, you have a keymoves tab and a protocols tab, yet when I add an upgrade that has both, neither tabs are populated. Now I understand WHY you're hiding stuff, but it's hiding none the less. Now, if I want to add a new keymove and there's no memory left, I need the ability to manage my keymove memory, so I need to be able to look at all my keymoves at once (like I can in IR) so I can decide if some of them are not really needed. Can you imagine how tedious that would be if I had to go through each upgrade to check whether it was using keymoves.
Now suppose I want to check which protocol upgrades are being used in my remote, in IR I can just go to the protocols tab and see, plus I can see the protocols in disassembled form so I can also see what they do, I can't do either of these using RMIR.
Bottom line, it's not essential that you
agree that we need to do these things, the fact is that we have a tool that does what we want today, so in order to get us to move over to a new tool, you're going to have to make it do what we want.
