RM 1.98b6 problem

wnewell · Post by **wnewell** » Tue Dec 01, 2009 4:45 am

Created and added 2 new device codes numbered 3000 Audio and 3001 VCR in RM w/o a problem. Uploaded to RCRP05B remote with rmir and all works well. But, when I dowmloaded from the remote the device numbers in the devices tab had changed to 0952 and 0953 respectively. I did not try and re-upload.

gfb107 · Post by **gfb107** » Tue Dec 01, 2009 6:36 am

Is that v1.98beta6 or v1.98beta6a? If not v1.98beta6a, please try again with that.

wnewell · Post by **wnewell** » Tue Dec 01, 2009 1:00 pm

It wasn't, but I just downloaded 6a and get the same results. With both only the device tab code numbers changed. The device code assignments in the General tab stayed 3000 and 3001.

wnewell · Post by **wnewell** » Mon Dec 07, 2009 4:32 pm

Just an update. The largest built in code in the RCRP05B I found was 2957 for Panasonic Audio device, so I changed all my device codes back to 2901-2909. Same thing happens when you download from remote with rmir 1.98b6a. Device codes get changed to 0852 etc., respectively. Don't know how high valid device codes go in the new remotes, but it's a lot higher than rmir can handle properly when downloading from the remote. No problem uploading them though, so even using the 3000 codes worked for an upload.

gfb107 · Post by **gfb107** » Mon Jan 25, 2010 11:07 pm

Please try RM v1.98beta7.

wnewell · Post by **wnewell** » Mon Mar 15, 2010 1:46 pm

gfb107 wrote:Please try RM v1.98beta7.

Sorry it took so long, but just got a couple more remotes and the same problem still exists.

setcode 3008, uploads fine. then when you download from remote the setcode shows it as 0960.

wnewell · Post by **wnewell** » Fri Apr 02, 2010 1:19 am

Greg, Have you had any time to look at this?

alanrichey · Post by **alanrichey** » Wed Apr 14, 2010 1:12 am

Found another bug with v1.98beta7. If you change the value of an OBC then select File > Save, the OBC value reverts back to the previous value. It basically means you cannot edit an existing RM file if you have made an error.

gfb107 · Post by **gfb107** » Wed Apr 14, 2010 5:54 am

wnewell wrote:Greg, Have you had any time to look at this?

No, sorry. Didn't see your post until now.

gfb107 · Post by **gfb107** » Wed Apr 14, 2010 6:27 am

alanrichey wrote:Found another bug with v1.98beta7. If you change the value of an OBC then select File > Save, the OBC value reverts back to the previous value. It basically means you cannot edit an existing RM file if you have made an error.

Don't really understand what you are saying here. What do you mean "if you have made an error"? Did you enter an invalid OBC? If that's the case, I don't consider this a bug - RM should not allow you to save invalid data.

Capn Trips · Post by **Capn Trips** » Wed Apr 14, 2010 6:51 am

Greg, I BELIEVE that Alan is saying that if you made a rmdu in which you erroneously entered the wrong OBC for a function (not something that RM would be able to identify), and subsequently go back and attempt to CHANGE that OBC value, RM is not allowing him to save that changed rmdu.

I've not seen this behavior myself, and it would seem a simple workaround would be to DELETE the erroneous entry and add a new one, but that doesn't answer Alan's concern directly.

gfb107 · Post by **gfb107** » Wed Apr 14, 2010 6:58 am

I think I figured it out. If you change the value of any cell, and then without pressing enter or giving any other cell the focus, you use File -> Save the change is lost.

The simple workaround is to press Enter after editing a cell, but I'll fix it.

alanrichey · Post by **alanrichey** » Wed Apr 14, 2010 10:47 am

Sorry, I was too quick to declare a bug there. I hadn't noticed that shifting the focus allowed the changed value to remain. I'll do a bit more testing next time

No need to fix it I think.

gfb107 · Post by **gfb107** » Wed Apr 14, 2010 7:35 pm

gfb107 wrote:
wnewell wrote:Greg, Have you had any time to look at this?
No, sorry. Didn't see your post until now.

I've found the problem. The fix will be in the next beta, tonight or tomorrow.

gfb107 · Post by **gfb107** » Wed Apr 14, 2010 7:35 pm

alanrichey wrote:Sorry, I was too quick to declare a bug there. I hadn't noticed that shifting the focus allowed the changed value to remain. I'll do a bit more testing next time No need to fix it I think.

I have a fix for this, will also be in the next beta.