Bug 12192 - issues with reskin() and hidden elements
: issues with reskin() and hidden elements
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: UI
: unspecified
: PC Other
: P1 critical with 1 vote (vote)
: 7.5.0
Assigned To: Richard Titmuss
:
Depends on:
Blocks: 12228 14804
  Show dependency treegraph
 
Reported: 2009-05-28 15:51 UTC by Ben Klaas
Modified: 2010-04-08 17:24 UTC (History)
8 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Klaas 2009-05-28 15:51:42 UTC
easily seen when NP auto switches to Fab4Remote UI, then back to Fab4Skin. The transport buttons are removed when switching to Remote skin (correctly), then after switching back to Fab4Skin the transport controls are absent.

There's also a UI design directive to remove buttons from the 3' UI when using IR, so this will be a problem there too.
Comment 1 Ben Klaas 2009-06-01 07:46:17 UTC
*** Bug 12206 has been marked as a duplicate of this bug. ***
Comment 2 Jim McAtee 2009-06-01 07:54:25 UTC
(In reply to comment #0)

> There's also a UI design directive to remove buttons from the 3' UI when using
> IR, so this will be a problem there too.

This should be rethought.  If you're close enough to the screen to touch it, the buttons should remain up and usable, whether or not you're using the IR.
Comment 3 Ben Klaas 2009-06-01 07:57:52 UTC
Matt, please comment here.
Comment 4 Weldon Matt 2009-06-01 14:56:04 UTC
> There's also a UI design directive to remove buttons from the 3' UI when using
> IR, so this will be a problem there too.

The directive was to provide a 3' option for IR in case the 10' version (big text) isn't good enough or ready enough to be our default upon launch.  That doesn't mean we can't show buttons when the user approaches the device.

I think we have some confusion regarding terminology.  I've been using the "3-foot" and "10-foot" terms to simply refer to the text size in the relevant skin, not as a literal description of how many feet away you're supposed to be to see a certain skin.  I'll refer to the different versions below as "big text" and "small text" to hopefully be more clear.  Here's the desired behavior:

(Use case: Either via default or by user setting, the "small text" skin is activated for remote).

- I interact with the device via touch while sitting right next to it.  I should see small text + buttons at this point.  (We've been calling this the "three-foot touch mode").
- (if proximity detection is on) I move away from the device.  After a very brief amount of time, the buttons go away (text size doesn't change in this case) - we've been calling this the "3-foot remote" mode, which I guess is a bad way to describe it).
- when I approach the device again, the buttons reappear (back to "three-foot touch mode.")

(Use case: Either via default or by user setting, the "big text" skin is activated for remote).

- I interact with the device via touch while sitting right next to it.  I should see small text + buttons at this point.  (We've been calling this the "three-foot touch mode").
- (if proximity detection is on) I move away from the device.  After a very brief amount of time, the buttons go away and the text size gets bigger - we've been calling this the "10-foot remote" mode.
- when I approach the device again, the buttons reappear and text gets smaller again (back to "three-foot touch mode.")

I hope that makes it more clear.  Apologies for the confusion, I think part of the issue has been that we've been talking about "10-foot" and "3-foot" modes just in design terms (and not implementation terms) for around 6 months now with no actual proximity detector.

Basically, there should be:

"Small text touch mode" (touch or within approx. 3 feet, small text, with buttons, no showbrieflies in NP)
"Small text IR mode" (farther than 3 feet, small text, no buttons, use showbrieflies in NP)
"Big text IR mode" (farther than 3 feet, big text, no buttons, use showbrieflies in NP)

The "big text touch" mode seemed to be one we would get "for free" but it's of much much less importance than the other three
Comment 5 Blackketter Dean 2009-07-28 13:02:49 UTC
Matt: is this all you need to say? OR should this go to Ben?
Comment 6 James Richardson 2009-07-29 06:57:17 UTC
*** Bug 13110 has been marked as a duplicate of this bug. ***
Comment 7 James Richardson 2009-08-18 20:39:16 UTC
These are marked as CXR, yet that milestone is over now.  Please re-target accordingly.
Comment 8 James Richardson 2009-09-14 15:16:31 UTC
Bumping Milestone
Comment 9 Philip Meyer 2009-09-24 12:19:17 UTC
I've been experiencing a lot of cases recently where the buttons disappear from the Touch screen, and no matter what I do, I can't get them back.

Don't think I'm doing anything to cause the buttons to be hidden.  i.e. not using IR, and proximity sensor is disabled (I think - can't find the setting now - if there is one, I'd have set it to disabled).
Comment 10 Ben Klaas 2009-09-30 11:20:42 UTC
Pushing this one Richard's way. Richard, best way to understand this one is to go to the NP screen and have it switch between 10' and 3' UIs
Comment 11 Richard Titmuss 2009-09-30 12:34:29 UTC
*** Bug 11915 has been marked as a duplicate of this bug. ***
Comment 12 Ben Klaas 2009-10-02 07:38:14 UTC
Specifically, steps to reproduce:

1. Using Touch interface, go to Now Playing screen
2. Use IR remote to play/pause track. Skin should shift to 10' UI
3. Touch the screen to shift it back to 3' UI

observer at bottom toolbar does not come back
Comment 13 James Richardson 2009-10-16 13:26:03 UTC
*** Bug 14804 has been marked as a duplicate of this bug. ***
Comment 14 SVN Bot 2009-10-20 07:35:16 UTC
 == Auto-comment from SVN commit #7906 to the jive repo by richard ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7906 ==

Bug #12192
Fix hidden elements when switching skins.
Comment 15 Chris Owens 2010-04-08 17:24:16 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!