Question on Multiple EventStrings for one command

[Ron]

Cannot recreate. please give a step by step description.

[Ron]

Where does it show this ? Please please give a step by step walkthrough how I can recreate this. I do not have time to hunt for bugs right now.

[Ron]

I don't know if this really is a problem though because I just noticed that the name of the plugin used to create the event is listed above the dot-matrix eventstring.

Thats what I thought :-)

[vynce]

I think I know what they're talking about. I don't think this is a bug, but just a confusing interface problem. It does not affect functionality in any way that I can see.

Here is how to recreate it:

1. Have at least 1 input plugin (i.e. an IR device plugin) enabled so that you have different choices in the drop-down box next to the learn button.
2. Create two commands and add eventstrings string to both of them.
3. Working with the first command now.
4. Select Girder Event from the drop-down box next to the learn button.
5. Click learn and type in anything for the eventstring.
6. Working with the second command now.
7. Select All from the drop-down box next to the learn button.
8. Click learn and press a button on your remote.
9. Now click on the eventstring for command #1.
10. The drop-down box next to the learn button will still show All instead of changing to Girder Event which that eventstring was learned as.

I don't know if this really is a problem though because I just noticed that the name of the plugin used to create the event is listed above the dot-matrix eventstring.

[vynce]

The item selected in the drop-down box next to the learn button is only to specify which device you want to use for that event when you click the learn button. It does not tell you which device that event uses when you select that eventstring later. The device associated with that eventstring will always be listed just above the dot-matrix eventstring as shown in the screen shots.


I notice that if I change one of the event strings under a command to type "Girder", all event strings change from "ALL" to "Girder".

Doing this does not actually change the device associated with all those eventstrings but rather sets the device to use to create a new eventstring.

I hope this all makes sense now :). If not, maybe someone else can explain it differently/better.

Image1 (http://www.vynce.kicks-ass.net/Girder/Eventstring1.gif)
Image2 (http://www.vynce.kicks-ass.net/Girder/Eventstring2.gif)
Image3 (http://www.vynce.kicks-ass.net/Girder/Eventstring3.gif)

Edit: Images converted to links to reduce page load time.

[vynce]

I understand what you mean. It does make it kind of difficult if you have to re-learn a whole lot of eventstrings that all use different plugins, because then you have to manually switch the plugin in the drop-down box for each eventstring. Maybe Ron can change how that functions sometime (?).

[stevech]

Girder 3.2... I have multiple possible event strings for each of many commands. Some event strings are from IR receivers (irMAN) and some are from Girder events (-eventstring xxx command line).

I notice that if I change one of the event strings under a command to type "Girder", all event strings change from "ALL" to "Girder".

Does this mean you can or cannot mix event string sources for a single command?

[stevech]

now I'm a bit more confused!

[stevech]

I think I get it - just ignore what the drop-down box for defining the eventstring type (ALL, Girder).

But !!

If I need to revise the event string, such as to change the Girder eventstring or the IR code for that type, I find that I have to change the dropdown for ALL or Girder before clicking LEARN else it tries to learn from the wrong eventstring source. That is, it will present the pop-up for a girder event even though the active eventstring is an IR one and my intent is to re-learn the IR command.

I can work-around manually, just a point of possible confusion.

[Icthus]

I have the same thing, but it doesn't actually change the other eventstrings. What I've noticed is that when you change the event type to Girder (or DVDSpy, etc...), that's what shows up regardless of which eventstring you have selected.

I'm not sure why it does this, but it doesn't change the behavior of the evenstrings for me.