On Wed, Dec 5, 2012 at 11:29 AM, Joey Morris <span dir="ltr"><<a href="mailto:rjmorris@nc.rr.com" target="_blank">rjmorris@nc.rr.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Christopher Kerr <<a href="mailto:mythtv@theseekerr.com">mythtv@theseekerr.com</a>> wrote on Wed, Dec 05, 2012 at 11:02:48AM +1100:<br>
<div><div class="h5">> On Wed, Dec 5, 2012 at 10:37 AM, Yeechang Lee <<a href="mailto:ylee@pobox.com">ylee@pobox.com</a>> wrote:<br>
><br>
> > Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> says:<br>
> > > No, Watch Recordings used the INFO to show info (and *context* menu) on<br>
> > > the selected recording. It was changed because many people whined that<br>
> > > "Any sane user interface doesn't need 2 menus," so now we have 2 menus<br>
> > > and an impossible to describe user interface ("Hit MENU, and if you<br>
> > > don't see <whatever>, hit MENU, again...").<br>
> ><br>
> > How is this harder to use, or describe, than telling people they have<br>
> > to bind two separate buttons and remember what functions appear in<br>
> > which menu? Besides, you and I both know that the Watch Recordings<br>
> > menu is context-sensitive and will almost always do the right thing.<br>
> ><br>
> > > Again, INFO was always for information/context menu and MENU was for<br>
> > > "main" menu (i.e. like the one you'd have at the top of the<br>
> > > application, versus the right-click/context menu).<br>
> > ><br>
> > > What Mike says is 100% accurate (and not the revisionist history of<br>
> > > those who complained until MENU got changed).<br>
> ><br>
> > Please spare us the patented Michael T. Dean passive aggressiveness.<br>
> ><br>
> > No, it makes no sense, in an environment with relatively limited<br>
> > buttonspace (I have a programmable remote with softkeys, but most<br>
> > don't), to have two menus that are completely separate and require two<br>
> > different buttons. You were wrong when mythtv-users had this debate<br>
> > after 0.22 was released. More importantly, other developers disagreed<br>
> > with you; otherwise the change would never have occurred.<br>
> ><br>
><br>
> Well, as a user, with no affiliation with the developers: I liked it better<br>
> before, too. MTD's analogy between application menus and right click menus<br>
> is right on the money - changing the way the interface works does NOT<br>
> belong in the same context as altering the details of a specific<br>
> recording/video.<br>
><br>
> If you use a remote with too few buttons, that's your problem - I'd rather<br>
> that you and others didn't ruin my experience to solve your own issues. The<br>
> interface was logical, now it isn't.<br>
<br>
</div></div>I don't understand the problem with the current interface in Watch<br>
Recordings. With a recording selected, INFO gives me the recording's<br>
details. With a recording selected, MENU gives me the context menu for<br>
that recording. With a group selected, MENU gives me a menu of mostly<br>
group-related items. How is this illogical?<br></blockquote><div><br></div><div>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.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Mike's description of the old method (INFO shows info *and* a context<br>
menu) is what sounds illogical to me. I don't think the analogy to<br>
left and right mouse buttons is apt, because the remotes don't say<br>
left-click/right-click, they say Menu/Info.</blockquote><div><br></div><div>I have never, ever, pressed the Info button and wanted the "Info" display - frankly, it's something I use so infrequently that I'd rather it was only a menu item on the "Info Menu", i.e. the menu you used to get when you hit Info.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> (And seriously, how many remotes don't have both a Menu/Options/Settings<br>
> button and an Info/"i"/Details button?)<br>
<br>
</div>The fairly popular MCE remotes have an Info button but not Menu. As<br>
another user said, I get around that by remapping the Windows button to<br>
Menu. It's set up to take you to the home screen by default, I believe.</blockquote><div><br></div><div>In truth, I use an MCE remote - this is such an obvious mapping that it had never occurred to me that people might use it any other way - even when I used Windows MCE, I thought of it as the "Menu" button, because it took me back to the menu!</div>
<div><br></div><div>- Chris </div></div></div>