Posts: 26,215
Joined: Oct 2003
Reputation:
187
@migueld: While I basically agree with you, there are circumstances where doing something other than "play" by defaultmay be more useful for a particular scenario.
In some situations having the "Enter/Select" button actually give you a choice of which action to perform on an item makes quite a bit of sense. For instance, I've always liked the idea of "Select" on a movie giving you the movie information rather than playing directly. After all, the default action from there could well be play, and it's not as if it slows you down much. Once you have that separate screen, then many of the context items become irrelevant, as you just do them directly in there.
While this works well for videos, it doesn't work so well for music where you don't want to be going constantly through a separate menu. On the other hand, having the default action be "Queue" (as an option, ofcourse) in music gives a simple way to do a jukebox style mode.
Cheers,
Jonathan
Posts: 4,549
Joined: Dec 2007
Reputation:
17
topfs2
Team-Kodi Developer
Posts: 4,549
I'd go so far as to say it's a great feature for movies but not so much for TV Shows, so there is a context difference there aswell which is probably a good idea to take into account.
If you have problems please read
this before posting
Always read the
XBMC online-manual,
FAQ and
search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the
forum rules.
For troubleshooting and bug reporting please make sure you
read this first.
"Well Im gonna download the code and look at it a bit but I'm certainly not a really good C/C++ programer but I'd help as much as I can, I mostly write in C#."
Posts: 26,215
Joined: Oct 2003
Reputation:
187
If you either don't map it or map it to context menu, in either case you need to define it somewhere - this is my point: Separate things for "Select" in different sections may make sense, thus there is more than one "context" to define (eg "focused on a video file" versus "focused on a music file" may command different mappings).
The absolute first thing to do before this will take off is to define those contexts. The smaller the set of contexts the better. It may be that we don't feel we need a separate "focused on playable item" context in each view.
The code side or making it work from the UI is the easy bit in comparison.
Cheers,
Jonathan
Posts: 26,215
Joined: Oct 2003
Reputation:
187
2009-10-17, 03:05
(This post was last modified: 2009-10-17, 03:05 by jmarshall.)
Yeah, it's a tricky one when the skin is involved. Currently I guess the skin does dictate some of what happens on navigation - they can make directional movements change screen (MC360) or start playing videos (Aeon) so perhaps allowing the skin to define the action isn't entirely out of the question, though I remain unconvinced that it's really the skinners role to dictate something quite like this.