RMIR: Prototype IR function in RM

Discussion forum for JP1 software tools currently in use, or being developed, such as IR, KM, RemoteMaster, and other misc apps/tools.

Moderator: Moderators

ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

I hope this won't derail your deliberations :)
Here is a screeenie of what started this whole thing. Likely different expectations on my part.
http://www.hifi-remote.com/forums/dload ... e_id=13057
As I mentioned before, I was just trying to see what's there (did I put functions in the uprade? did I not?), minimize, and get back to look at keymoves which I couldn't do minimizing.
The Device editor didn't display stuff correctly anyway, so it might be a moot point.
Perhaps SavingAs there is not expected to work, because I can't imagine how from just the RMIR keymoves there's a way for RMIR to know what, if anything, is or is not in the device upgrade.
And without a display of buttons like in IR, I really could not tell.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride :)
Barf
Expert
Posts: 1523
Joined: Fri Oct 24, 2008 1:54 pm
Location: Munich, Germany
Contact:

Post by Barf »

I looked into the code a bit more, and it appears that it was never intended to be able to run the DeviceUpgradeEditor mode-less. In GeneralPanel.editUpgradeInRow, the existing device upgrade is effectively (deep) cloned, and at the end (DeviceUpgradeEditor,actionPerformed()) copied back.

Liz, I agree with your criticism -- it is like having a blueprint to a house, and only be able to access either the exterior ("rmir") or a single room (device upgrade) at a time. But we will have to live with it, or make a fairly substantial re-factoring.
CyberSimian
Posts: 90
Joined: Thu Oct 24, 2013 8:10 am
Location: Southampton, UK

Post by CyberSimian »

mathdon wrote:It appears that I did this in April 2014. I have no recollection of doing so, or why I did it. There must have been some reason. I'll try to think what it might have been, and if there is some other way of meeting it.
Was this change in response to bug 16 in this post:

http://www.hifi-remote.com/forums/viewt ... ht=#111142

Bug 16 was:

(16) (BUG) In the "Device Upgrade Editor", the "Minimise" button (top right of window title bar) does not work correctly. The minimise animation occurs, but the minimised window remains on the screen.

-- from CyberSimian in the UK
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

CyberSimian wrote:
mathdon wrote:It appears that I did this in April 2014. I have no recollection of doing so, or why I did it. There must have been some reason. I'll try to think what it might have been, and if there is some other way of meeting it.
Was this change in response to bug 16 in this post:

http://www.hifi-remote.com/forums/viewt ... ht=#111142

Bug 16 was:

(16) (BUG) In the "Device Upgrade Editor", the "Minimise" button (top right of window title bar) does not work correctly. The minimise animation occurs, but the minimised window remains on the screen.
Yes, it was. It is all coming back to me now. I think that what happened was as follows. Rightly or wrongly it was believed, by me and others, that the Device Editor window was modal. If you clicked on its title bar it did not gain the focus, that remained with the editor window. That was enough for me to believe, without explicitly trying it, that the whole window was disabled. Barf has discovered that is not the case now - the window remains functional even though the title bar looks as if it is disabled. I am not aware of anything that may have changed the Device Editor from modal to non-modal. As Barf has also discovered, it is not trivial to make it modal, so I am inclined to believe that it always was non-modal and we were all mistaken. But whether that is so or not, what IS the case is that I acted in the belief that it was modal.

I presume the original behaviour, that before my "fix" of April 2014, was to mimic the behaviour of a real modal window that doesn't have a minimize button, so it effectively made that button ineffective. My fix allowed minimization, but so as not to leave a disabled window on the screen that one could do nothing with, I also minimized the main window.

I have now followed Barf's mods to make the Device Editor genuinely modal. Minimizing it but leaving the main window then gives a window on the screen that cannot even be moved, never mind itself minimized. That is not acceptable to me, so I have left active the code that minimizes the main window when you minimize the Device Editor.

However, I like happy users so I have also put in an option to make the Device Editor non-modal. Minimizing the editor then leaves an active main window on the screen. The problem with this is that if you edit the main window while the editor is still open, you can get inconsistencies. This option has to be "at your own risk". To emphasise this, when the editor is open then the status bar of the main window displays a warning "DO NOT EDIT THE MAIN WINDOW WHILE THE DEVICE EDITOR IS OPEN". I consider this an advanced option, so you will find it under Options/Advanced/Use non-modal Device Editor. Once selected, this option persists in future invocations of RMIR until deselected. It is valid to deselect the option while the Device Editor is open, in which case it will change from non-modal to modal while open.

I will post a new RMIR shortly with this behaviour.
Graham
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

ElizabethD wrote:The Device editor didn't display stuff correctly anyway, so it might be a moot point.
I cannot tell from your jpg whether the display is correct or not. Perhaps the missing functions are on the External Functions tab? If you want me to look into it, please post the files you were using.
ElizabethD wrote:Perhaps SavingAs there is not expected to work, because I can't imagine how from just the RMIR keymoves there's a way for RMIR to know what, if anything, is or is not in the device upgrade.
I don't understand what you were trying to do, so cannot comment. But remember that there is only one application - the Device Editor is part of RMIR, not a separate invocation of RM - so RMIR holds all the data displayed in both the main and editor windows.
Graham
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

Mini upgrade
http://www.hifi-remote.com/forums/dload ... e_id=13098
I think I see what's going on and think you just confirmed - the disconnect between the two windows or in my brain.
This upgrade has 2 functions but no buttons. 2 keymoves are made in IR, manually.
The Device editor title is "Device upgrade" - so I assumed I'll see what's in KM device upgrade.
But it's not. It's what RMIR reports which would be equivalent to what's in IR buttons display which one deos not save as device upgrade of course.
Why then would I want to SaveAs this thing without its functions?

I haven't yet absorbed modal/nonModal answer of yours, but the solution sounds interesting.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride :)
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

ElizabethD wrote:Why then would I want to SaveAs this thing without its functions?
I'm not with you at all. "Save As" in the Device Upgrade Editor saves a .rmdu file, complete with functions. Why do you think the functions are missing, when there is a Functions tab in the editor?

Edit: When I load your mini-upgrade into the Device Upgrade Editor of RMIR, or separately into RM, I see the same two functions as in your posted jpg.
Graham
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

using alpha27c

Thanks again for answering. I no longer know what I'm doing. I think it was from raw device upgrade that come in without functions after I had some other troubles with RMIR wanting me to assign a device and I did not want to and goofed not seeing Cancel :(

New question: This TV upgrade in KM has 3 buttons on the Keymove tab, they're not in the normal Upgrade section (shifts usually), but in the Keymoves section to copy/paste.
http://www.hifi-remote.com/forums/dload ... e_id=13099
Other than manually - how do I bring it in? No big deal really but I thought I'll ask. It's confusing me when .rmdu files don't have Keymoves tab, so ones such as this might get lost in translation from KM-IR to RM-RMIR system.
Since you don't have KM - screenie of the tab posted.
When importing keymoves such as these, IR reminds that the device (AUD) has to be in.
http://www.hifi-remote.com/forums/dload ... e_id=13100
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride :)
derek1234
Posts: 3
Joined: Tue Jun 26, 2007 8:16 pm

Bug in 2.02a and Linux

Post by derek1234 »

This might be a moot bug, but I downloaded the latest version from SourceForge which appears to be 2.02a. I am running it under Ubuntu 14.04. When I start the Rmaster.sh the program started fine, but when I try to open a .rmdu file, nothing happens, the file dialog box closes and I go right back to the RM IR program screen. So I fired up version 2.00, and it works as expected, when I try to open a .rmdu file, it opens a new remotemaster program window.

Sorry if this has already been addressed, but I am still quite a novice at this. Love the program by the way.
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

derek1234 wrote:This might be a moot bug, but I downloaded the latest version from SourceForge which appears to be 2.02a.
Version 2.02a is two years old and is about to be replaced. Please try the latest development version, v2.03 Alpha 27c, and let us know if this still causes the same problem.
Graham
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

ElizabethD wrote:Other than manually - how do I bring it in? No big deal really but I thought I'll ask. It's confusing me when .rmdu files don't have Keymoves tab, so ones such as this might get lost in translation from KM-IR to RM-RMIR system.
Oh ye of little faith! They don't get lost. Try it. Open RM and load your .txt file. Look at the Buttons tab. You will see the assignments of these functions to buttons. Look at the Functions tab. You will see the OBC, hex etc of these functions. Look at the Output tab. You will see them exported there as Key Moves. If you instead load it into the Device Upgrade Editor in RMIR, you will see the same thing, but also, if you press OK and assign the upgrade to a device button, you will see the key moves (shaded gray) also in the Key Moves tab
Graham
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

Please see this announcement of RMIR v2.03 Alpha 28, a substantial change from the Alpha 27 series. All users of the Alpha development versions are encouraged to try it.
Graham
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

mathdon wrote:
ElizabethD wrote:Other than manually - how do I bring it in? No big deal really but I thought I'll ask. It's confusing me when .rmdu files don't have Keymoves tab, so ones such as this might get lost in translation from KM-IR to RM-RMIR system.
Oh ye of little faith! They don't get lost. Try it. Open RM and load your .txt file. Look at the Buttons tab. You will see the assignments of these functions to buttons. Look at the Functions tab. You will see the OBC, hex etc of these functions. Look at the Output tab. You will see them exported there as Key Moves.
No I do not. Just the base TV volume keys there. Nothing as Keymoves to AUD.
mathdon wrote:If you instead load it into the Device Upgrade Editor in RMIR, you will see the same thing, but also, if you press OK and assign the upgrade to a device button, you will see the key moves (shaded gray) also in the Key Moves tab
Nope, not here either.
To confirm, I just redid all this from scratch, using your exact instructions.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride :)
mathdon
Expert
Posts: 4725
Joined: Tue Jul 22, 2008 8:53 am
Location: Cambridge, UK

Post by mathdon »

ElizabethD wrote:No I do not.
OK, I misunderstood what was missing. I think I see now. As far as I can tell, it is not a bug in RM, it is something never implemented. Greg wrote the import code. I have no understanding of the structure of a KM .txt file and there is no way I can implement it. Perhaps Greg can find time to look at it, otherwise I am sorry, it will have to stay missing.
Graham
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

This is not supported, and I don't think it ever will be.

IMO, these keymoves seems inconsistent with the concept of a device upgrade. A device upgrade defines the functions available to control a device, and a mapping of those functions onto the buttons when that update is bound to a device button. Assigning functions to buttons in a different device mode (in this case AUX) is a cross-device configuration, and doesn't belong in a device upgrade. Again, that's just my opinion.

Note that RMIR allows you to create keymoves using the names of functions from any installed device upgrade (even those that haven't been mapped to a button), so you don't need to copy/paste the EFC or Hex to do it
Post Reply