[mythtv-users] Programming remote button bindings (WAS: What major features are planned for 0.27?)

[jedi]

On Wed, Dec 05, 2012 at 03:18:26PM +1100, Christopher Kerr wrote:
> On Wed, Dec 5, 2012 at 2:54 PM, Joey Morris <rjmorris at nc.rr.com> wrote:
> 
> > Christopher Kerr <mythtv at theseekerr.com> wrote on Wed, Dec 05, 2012 at
> > 12:16:12PM +1100:
> > > On Wed, Dec 5, 2012 at 11:29 AM, Joey Morris <rjmorris at nc.rr.com> wrote:
> > >
> > > > Christopher Kerr <mythtv at theseekerr.com> wrote on Wed, Dec 05, 2012 at
> > > > 11:02:48AM +1100:
> > > > > On Wed, Dec 5, 2012 at 10:37 AM, Yeechang Lee <ylee at pobox.com>
> > wrote:
> > > > >
> > > > > > Michael T. Dean <mtdean at thirdcontact.com> says:
> > > > > > > No, Watch Recordings used the INFO to show info (and *context*
> > menu)
> > > > on
> > > > > > > the selected recording.  It was changed because many people
> > whined
> > > > that
> > > > > > > "Any sane user interface doesn't need 2 menus," so now we have 2
> > > > menus
> > > > > > > and an impossible to describe user interface ("Hit MENU, and if
> > you
> > > > > > > don't see <whatever>, hit MENU, again...").
> > > > > >
> > > > > > How is this harder to use, or describe, than telling people they
> > have
> > > > > > to bind two separate buttons and remember what functions appear in
> > > > > > which menu? Besides, you and I both know that the Watch Recordings
> > > > > > menu is context-sensitive and will almost always do the right
> > thing.
> > > > > >
> > > > > > > Again, INFO was always for information/context menu and MENU was
> > for
> > > > > > > "main" menu (i.e. like the one you'd have at the top of the
> > > > > > > application, versus the right-click/context menu).
> > > > > > >
> > > > > > > What Mike says is 100% accurate (and not the revisionist history
> > of
> > > > > > > those who complained until MENU got changed).
> > > > > >
> > > > > > Please spare us the patented Michael T. Dean passive
> > aggressiveness.
> > > > > >
> > > > > > No, it makes no sense, in an environment with relatively limited
> > > > > > buttonspace (I have a programmable remote with softkeys, but most
> > > > > > don't), to have two menus that are completely separate and require
> > two
> > > > > > different buttons. You were wrong when mythtv-users had this debate
> > > > > > after 0.22 was released. More importantly, other developers
> > disagreed
> > > > > > with you; otherwise the change would never have occurred.
> > > > > >
> > > > >
> > > > > Well, as a user, with no affiliation with the developers: I liked it
> > > > better
> > > > > before, too. MTD's analogy between application menus and right click
> > > > menus
> > > > > is right on the money - changing the way the interface works does NOT
> > > > > belong in the same context as altering the details of a specific
> > > > > recording/video.
> > > > >
> > > > > If you use a remote with too few buttons, that's your problem - I'd
> > > > rather
> > > > > that you and others didn't ruin my experience to solve your own
> > issues.
> > > > The
> > > > > interface was logical, now it isn't.
> > > >
> > > > I don't understand the problem with the current interface in Watch
> > > > Recordings. With a recording selected, INFO gives me the recording's
> > > > details. With a recording selected, MENU gives me the context menu for
> > > > that recording. With a group selected, MENU gives me a menu of mostly
> > > > group-related items. How is this illogical?
> > > >
> > >
> > > Because I don't think of that list as being "groups" - I have it
> > configured
> > > to only display All Programs and program names, not recording groups or
> > > anything else. As such, moving over to the "Series List" panel to change
> > > group options makes no damn sense to me at all, nor any of the other
> > users
> > > in the house.
> >
> 
> 
> > For someone like me who didn't use MythTV before this change, your
> > preferred method would be frustrating. Suppose I have a recording
> > highlighted and I want to access its menu. Logically, I'll hit the
> > MENU button. But then the Group Menu pops up! What? Oh, I need to hit
> > the INFO button to see the menu, not the MENU button.
> >
> > I'd summarize the two alternatives like this:
> >
> > 1) Press MENU over widget A to see widget A's menu. Press MENU over
> >    widget B to see widget B's menu.
> > 2) Press MENU no matter where you are to see widget A's menu. Press
> >    INFO no matter where you are to see widget B's menu.
> >
> > Do you really consider (1) the illogical one? If so, I think you're
> > confusing "illogical" with "inconvenient given my usage patterns".
> 
> 
>  Except that you've got (2) wrong. It was:
> 
> (2) Press MENU no matter where you are to see a menu of globally relevant
> options (recording groups, parental filtering and so on). Press INFO over
> Widget A to see a menu specific to doing things with Widget A. Press INFO
> over Widget B to see a menu specific to doing things with Widget B.
> 
> Now are people seeing my "Application Menu" vs "Right click menu" argument?
> In Word, I can pull up the File menu any time I like (well, when it had one
> I could, anyhow). To do something with a specific paragraph, I'd highlight
> it and right click it to pull up a context menu. See how that's like (2),
> and akin to how every other application in the universe works? Logical.

INFO does not imply anything to do with menus.

INFO implies information about something. Hopefully it makes some sense in context.

MENU is something else entirely. Having a global menu seems like a cool idea but
it should not displace a context sensitive menu and force it to be associated with
something that's completely counter-intuitive.

MENU is not INFO

GLOBAL_MENU is handy but shouldn't displace MENU so as to make it more confusing.