Bugzilla – Bug 15140
Automatic skin switching to default skin after timeout
Last modified: 2011-01-19 09:25:30 UTC
The current skin switching behavior on the Touch doesn't work good with my typical placement a bit away from the sofa. In this case, if you use the touch screen you always have to manually click something on the remote to get it to enlarge the text so its visible from the sofa. I use the remote most of the time and I only want small texts while I'm standing beside the device and navigating through the touch screen. When I haven't touch the touch screen for a while it means that I've gone to the sofa and needs large text again. My personal preference would be two different options: - Option 1: Select default skin - Option 2: Select if automatic skin switching should be enabled The behavior would be: 1. If automatic skin switching is turned off: - It would always use the selected default skin and never switch to the other skin 2. If automatic skin switching is enabled and default skin is small: - It would only use the large/remote skin when the user pushes the IR remote - It would always switch back to small skin a little while of inactivity after a IR remote push 3. If automatic skin switching is enabled and default skin is large/remote: - It would only use the small skin when the user recently have touched the screen - It would always switch back to large/remote skin after a little while of inactivity As far as I can see a behavior like this would make it possible for everyone to configure it like they want. In the future the proximity sensor can also be added to this scheme so in scenario 3 it wouldn't switch back to large skin as long as the proximity sensor don't show that someone is near the device. It would also in scenario 3 be able to use the proximity sensor to switch to small skin when someone is getting close to the device. However, the scheme would work good for everyone even without the usage of the proximity sensor.
It is a great idea, but not as great as 'get MiniSC working' :)
Moving lower-priority bugs to next target
This is already being brought up in the forums: http://forums.slimdevices.com/showthread.php?t=77406 I like the very simple suggestion of adding a third skin option: - Touch Skin (defaults to small text) - Remote Skin (defaults to large text) - Idle Skin The Idle Skin would be invoked after a timeout with no user input. The timeout should be the same as used before bringing up the Now Playing screen, which is the main reason for this request. The selections for the Idle Skin would be: No Change (default) // equivalent to the current behavior Small Text Skin Large Text Skin
There is no workaround for this from the touch screen interface -- the only way to switch from the small text skin back to the large text skin is to hit a button on the remote. Thus if you change the playlist, then go sit at the dining table (or wherever the remote isn't), you're stuck with the unreadably small text. This is a big failure in an otherwise great product.
Matt Weldon isn't available to us any more. Please vote for this bug to make sure it appears in our priority list!
There's no skin auto-switching any more, so I'm inclined to say this bug can close. paradigm now is to have a user-configurable skin for Touch skin (defaults to "small text") and Remote skin (defaults to "large text"). Any Touch input will cause it to switch to whatever the user has configured for the Touch skin, any remote input will cause it to switch to whatever the user has configured for the Remote skin. Erland, you okay with this closing?
(In reply to comment #6) > Any Touch input will > cause it to switch to whatever the user has configured for the Touch skin, any > remote input will cause it to switch to whatever the user has configured for > the Remote skin. > Erland, you okay with this closing? I am absolutely not okay with closing this. The skin selection behavior continues to be the most broken aspect of the Touch. To be clear, here's the behavior that *I* want from the Touch: *) By default assume that the user is far away (on the couch), and use a skin designed to be read from a distance, and controlled with a remote (big fonts, arrows instead of buttons, etc.). *) When I touch the screen, switch to a skin optimized for direct touch interaction (smaller fonts, buttons, more information density). *) After some decent interval with no touch interaction, switch to the distance skin. I'm quite aware that this isn't what everyone would want (eg. someone who puts the unit on their desk), so there will need to be some configurability. I think Erland's description is overly complex, while Jim McAtee's in comment #3 is clearer, and probably easier to implement.
Okay, taking the bug ownership back, and flagging for another bug_meeting discussion
(In reply to comment #6) > There's no skin auto-switching any more, so I'm inclined to say this bug can > close. > > paradigm now is to have a user-configurable skin for Touch skin (defaults to > "small text") and Remote skin (defaults to "large text"). Any Touch input will > cause it to switch to whatever the user has configured for the Touch skin, any > remote input will cause it to switch to whatever the user has configured for > the Remote skin. > > Erland, you okay with this closing? You haven't solved the problem, but you decide what you want to prioritize and I will accept it. So feel free to close it if you don't feel this enhancement is important. The only thing I ask is that you do the same with all the other enhancements you don't intend to prioritize. I've personally never understood the reason to keep enhancements open with target="Future" which you know you never are going to implement. If you want to implement it and just didn't understand the request, both my initial description and Jim's description in comment#3 solves the problem, it doesn't matter which one that gets implemented. I've personally solved the problem by stop using the touch screen on the Touch, this way it never switches to the small skin.