Commands not auto-selected if "Don`t send IR commands&q

[Ron]

The whole idea of that option is that Girder doesn't excute the commands when it is the foreground window, thus it also doesn't select any commands. This way Girder doesn't move the current command while you are working on it. This is by design behaviour.

[Ron]

Not currently. I have been thinking about something like this though.

update: Implemented in next beta.

[John777]

This has probably been covered here and I just can't find it. But I just upgraded from 3.0 to 3.2, and I think I've found a bug that makes it hard for me to manage the remote codes for all my commands.

The bug occurs when the "Don`t send the IR commands when Girder is the Foreground window" option is enabled. In that case, when I press a button on my remote while the Girder window is in the foreground, Girder does not automatically select the command that matches that IR code.

The only way I can easily see which command matches an IR code is to disable that preference (since I have a huge number of commands). But that is a real problem, because many of my commands are not things that I want to be executing when they're not needed.

Is there any way around this in the current version?

Thanks,
John

[John777]

The whole idea of that option is that Girder doesn't excute the commands when it is the foreground window, thus it also doesn't select any commands. This way Girder doesn't move the current command while you are working on it. This is by design behaviour.


Is there any way for me to press a button on my remote and have Girder show me which command uses that IR code, without Girder also executing that command?

Thanks,
John

[John777]

update: Implemented in next beta.


Awesome. Thanks again.

John