Won't be able to do much testing here in the short term, Peter, since my
time is focused on fixing Radio alarm functionality.
This is fabulous stuff, though! Thanks very much for this excellent
enhancement.
Maybe I'll be able to get some testing in next week sometime after my
daughter has g
I thought about waiting until the 25th to post this, but I expect I
won't have much time to do additional testing, so here goes...
If you're game, I just posted a version 2.4.0 to my *test* repository,
http://www.tux.org/~peterw/slim/slim7/repodata-test.xml, that implements
the second option. If
I agree that the second approach sounds like the most desirable.
It would be great to provide a checkbox in the per-player options for
each button specifying whether to 'override' the global button behavior.
I guess this would really just be the same as an 'enable' button,
actually. The point
My preference would be for the second of these (per-player and global
settings).
If there was a way to select between the global setting, the player
specific setting or no setting for each preset on each player that would
be a bonus.
BTW: thanks for this plug-in, it has been very useful. I'm us
I'll give it some thought. My initial goal with KidsPlay was making a
kid-ready IR remote, and I wanted the kid's remote to do the same thing
on all players, thus the global configuration. But I understand where
you're coming from.
There are three obvious approaches:
- per-player macros for
I've got Kidsplay installed (very nice tool, Peter, thank you), but am
wondering if there is a way to bypass the global preset button behavior
that seems to be required...? Global behavior is very useful in some
cases, but context sensitive behavior is certainly needed too. I
understand that if
