JP1 Remotes

[gfb107]

I've figured out the issues you found. I should have a new beta for you to try later today.

I don't really know what's going on with the 0042 protocol. Either it isn't actually present in your remote, or the variant in your remote is different and incompatible with the protocols.ini definition. I'm afraid you'll need help from the real experts on this one.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[xnappo]

[gfb107]

I remember a bug like this in the very early days of RMIR. Thought this was fixed. Definitely want to fix this in the next beta.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[xnappo]

[gfb107]

I've just uploaded the Java version of v1.98beta8 that should address your issues. Working on the Windows standalone version now, but it takes a lot more work to build and a lot longer to upload.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[xnappo]

[gfb107]

The Windows version of RM v1.98beta8 is now available.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[xnappo]

Hi Greg,

Another minor problem - in the DSM definition window, the extender device selection macros do not show up. For my particular case, the temporary device selection (X_<dev>) is what I would normally use.

Thanks!
xnappo

[xnappo]

And another small one - when switching between two .rmir files, or downloading from a remote that doesn't match the .rmir file currently loaded, the 'Devices' tab does not update (it stays with what was previously loaded).

Thanks,
xnappo

P.S. I completed the experiment with starting from scratch and can confirm all the bugs you have fixed to date for me are fixed.

[dolivas27]

[wnewell]

Same thing happens with Linux java version. Luckily I didn't try and build anything with this. If you load an older upgrade, the data comes in right.

[gfb107]

I would expect both the Windows standalone and the pure Java versions (regardless of platform) to always behave the same.

The areas where this might not be true are:

1. Minor UI layout differences
2. Remote IO

_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[wnewell]

It's not just NEC1. It's all of them (At least all I tried). As long as you use an upgrade built with an earlier version and don't mess with the device params, beta 8 will work. But don't try and build an upgarde with this. It won't work unless device params or all null.

[jimdunn]

I'll just confirm that is the case for me too - changes to device number/ subdevice don't "stick" or cause fixed data to update - as though your typed changes aren't being "committed" - and they do indeed vanish if you switch tabs -or try to save the upgrade.

Could it perhaps be an unintended consequence of the recent "fix" for data not saving if you don't "move out of" a cell which alanrichey reported ?

[gfb107]

It's an unintended consequence of the fix for the "corruption of fixed data when multiple upgrades use the same protocol" that xnappo reported.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)