Problem with IR 8.00

[kdp99]

First a massive thanks to all who replied, and helped.

I have used the development version of IR with the new RDF and this is what I have found.

1 The devices button area problem goes away
2 The index out of bound problem is still there
3 I have gone back to an earlier IR file before I added the upgrade, and repeated the process with the new IR/RDF combination. The error message first appears when IR assigns the upgrade to a device. If it helps developers I have also posted the earlier IR file here

http://www.hifi-remote.com/forums/dload ... le_id=6823

Thanks again

Keith

[vickyg2003]

Graham,
There appears to be a problem with adding upgrades with keymoves. The RMDU posted is for the wrong remote. I am assuming Keith adjusted his RMDU file to show the proper remote, (which was not done with at least one of his previous upgrades). But even if I adjust the upgrade for the correct remote I get the index out of bounds problems. If I try to assign the code by hand after getting the index out of bounds problem, I t get the error message, "AdvCode object not found".

EDIT:

Also there appears to be a problem with switching remotes after using a remote that has validation. After looking at this user's problem, I then downloaded from my remote to help another user and I couldn't change any of my device setup codes on my remote! The type would change but not the setup number itself.

Keith there is a work around.

Start with your older oct07.IR file
Open the RM file
Change to your remote
Copy output
Switch to IR
Add New Device upgrade
When it prompts you to automatically assign the button answer
NO
Then go to the General tab
Assign the upgrade to the desired device key by hand.
Go back to the Device tab
EDIT the upgrade
Paste again
All the keymoves will now show up and no error is generated.

I'd also suggest deleteing the DVD/1503 upgrade since it has too many fixed data bytes, indicating that the RM file was not adjusted to be for the correct remote before it was added in IR.

[kdp99]

Graham,
There appears to be a problem with adding upgrades with keymoves. The RMDU posted is for the wrong remote. I am assuming Keith adjusted his RMDU file to show the proper remote, (which was not done with at least one of his previous upgrades). But even if I adjust the upgrade for the correct remote I get the index out of bounds problems. If I try to assign the code by hand after getting the index out of bounds problem, I t get the error message, "AdvCode object not found".

EDIT:

Also there appears to be a problem with switching remotes after using a remote that has validation. After looking at this user's problem, I then downloaded from my remote to help another user and I couldn't change any of my device setup codes on my remote! The type would change but not the setup number itself.

Keith there is a work around.

Start with your older oct07.IR file
Open the RM file
Change to your remote
Copy output
Switch to IR
Add New Device upgrade
When it prompts you to automatically assign the button answer
NO
Then go to the General tab
Assign the upgrade to the desired device key by hand.
Go back to the Device tab
EDIT the upgrade
Paste again
All the keymoves will now show up and no error is generated.

I'd also suggest deleteing the DVD/1503 upgrade since it has too many fixed data bytes, indicating that the RM file was not adjusted to be for the correct remote before it was added in IR.

Works a treat - Many thanks indeed !!!

[mathdon]

Vicky, many thanks for the very detailed diagnosis. It made finding the 'Index out of bounds' bug a lot easier. I have corrected it for the next development build. It was not of my making - indeed, Keith originally found it in IR 6.20. It is very specific. It occurs only when adding Device Upgrades containing keymoves to remotes that need three address parameters in their RDF DeviceButtons entries. The RDF spec says that these are mostly older 6805 and 740-based remotes. So perhaps it is not surprising that it has gone un-noticed for a long time.

I haven't yet had time to look for your bug, switching to a new remote from one that has code validation. Unfortunately that looks as if it has to be one of my making .
______________________
Graham

[mathdon]

Vicky, I've just tried to reproduce your switching bug, and failed. I opened Keith's .ir file for the URC-8550 (with my RDF, which has code validation) and then downloaded from my URC-7781. Changing device types and setup codes both worked fine. I also tried loading Keith's file and then loading a .ir file for a URC-6131 which I have for testing. I don't have that remote, so couldn't try a download, but all still worked OK.

Can you give a more detailed description of the circumstances in which you found the problem?
_______________
Graham

[vickyg2003]

I think it might be related to when I fell into the error with AdvCode not found, which you may have already fixed. I tried to reproduce the error without hitting an error, and couldn't do it. When I forced myself into the AdvCode not found, then downloaded from my remote, deleted some protocols and devices, added a protocol and device I found the code numbers locked.

When I did these steps without hitting the errors, I didn't get the problem.

I make so many false moves when I navigate through IR that it is hard to say exactly what I did. But I did get it to happen again after causing the error which hopefully nobody will see with the next release.

[mathdon]

Vicky, did you change RDF directories in the course of getting your locking-up problem? I have just been doing some testing in which I changed between two RDF directories, one of which had a valid RDF and the other an invalid RDF for the current remote. I got all sorts of nasty behaviour, some of which needed Task Master to close the errant IR instance.

I'm trying to see if there is a way to sort this out, but it would be nice to know if this might have been the source of your problem, also.
__________________
Graham

[vickyg2003]

Vicky, did you change RDF directories in the course of getting your locking-up problem? I have just been doing some testing in which I changed between two RDF directories, one of which had a valid RDF and the other an invalid RDF for the current remote. I got all sorts of nasty behaviour, some of which needed Task Master to close the errant IR instance.

No, I still think mine is a remnant of producing that AdvCode error by trying to do the keymoves without first adding the device with that strange upgrade. That is the only way I can reproduce the problem, and since you already fixed that, it should be fine in next release.

I'll keep my eyes open and my wits about me next time I'm in IR.