home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Skins
Popular Skins
aMPed
Unexpected Panel Flow
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1096631" data-attributes="member: 141969"><p>Yes, I am happy with the stack analogy (that is how I think of it too). And I accept that it is not necessarily an error, since one can argue usability and user expectation either way. (After making the original post, I checked to see what Windows Media Center does, and that does the same thing -- when you select the new channel from the EPG, WMC leaves the EPG on the panel stack.)</p><p></p><p>However, there are two ways of controlling panel stacks:</p><p>(1) When the user selects the next panel, the new panel is added to the stack (the current action).</p><p>(2) When the user selects the next panel, that panel <em>replaces</em> the current panel on the stack.</p><p></p><p>Whether you want (1) or (2) depends on the nature of the panels one is flowing through, and in a complex application (like MP) one would probably use both. When I selected the new channel in the EPG, my expectation had been that the EPG would exit back to full-screen TV, passing back the number of the channel to switch to (so the EPG would not be on the panel stack any more).</p><p></p><p></p><p>I will try to reproduce this again tomorrow, but using the DefaultWide skin. I will also try using a keyboard instead of a remote control, and see if that makes a difference. If it occurs on DefaultWide, I will capture the log files. If it does not occur on DefaultWide, it suggests that it is a problem with some aspect of the aMPed skin definition.</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1096631, member: 141969"] Yes, I am happy with the stack analogy (that is how I think of it too). And I accept that it is not necessarily an error, since one can argue usability and user expectation either way. (After making the original post, I checked to see what Windows Media Center does, and that does the same thing -- when you select the new channel from the EPG, WMC leaves the EPG on the panel stack.) However, there are two ways of controlling panel stacks: (1) When the user selects the next panel, the new panel is added to the stack (the current action). (2) When the user selects the next panel, that panel [i]replaces[/i] the current panel on the stack. Whether you want (1) or (2) depends on the nature of the panels one is flowing through, and in a complex application (like MP) one would probably use both. When I selected the new channel in the EPG, my expectation had been that the EPG would exit back to full-screen TV, passing back the number of the channel to switch to (so the EPG would not be on the panel stack any more). I will try to reproduce this again tomorrow, but using the DefaultWide skin. I will also try using a keyboard instead of a remote control, and see if that makes a difference. If it occurs on DefaultWide, I will capture the log files. If it does not occur on DefaultWide, it suggests that it is a problem with some aspect of the aMPed skin definition. -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Skins
Popular Skins
aMPed
Unexpected Panel Flow
Contact us
RSS
Top
Bottom