Bug 13564 - Support ALL functions of (Handle Brightness button on) old IR remotes
: Support ALL functions of (Handle Brightness button on) old IR remotes
Status: NEW
Product: SqueezePlay
Classification: Unclassified
Component: UI Input
: unspecified
: PC Windows XP
: P5 minor with 2 votes (vote)
: ---
Assigned To: Felix Mueller
:
Depends on: 11389
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-21 11:33 UTC by Jim McAtee
Modified: 2011-01-14 00:29 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2009-08-21 11:33:54 UTC
There's no way to control which remote anyone will grab to control Fab4, so some logical handling of buttons only found on old remotes would make sense.

I think the handling of the Brightness button should be similar to the way it worked with old players.  Cycle through several (5 or 6) preset brightness levels each time the button is pressed.  Maybe 10, 30, 50, 70, 90 or perhaps some other levels that make sense.

No other screen feedback is necessary.  No popups, toast, etc.
Comment 1 James Richardson 2009-08-21 12:14:26 UTC
*** Bug 13565 has been marked as a duplicate of this bug. ***
Comment 2 James Richardson 2009-08-21 12:15:22 UTC
Not just the Size/Brightness, but all other buttons as well
Comment 3 Jim McAtee 2009-08-21 12:35:11 UTC
Ok, if you want to put it all in one bug then there needs to be a consensus on how to treat each button with respect to the new UI and display model.

* Size:

On Fab4 I think the Size button could toggle between the 10ft and 3ft skins.

* Now Playing:

The new remote has a 'Home' button that currently toggles between Home and the Current Playlist screens. (Is that the desired behavior?  I would think it should go between Home and Now Playing or else cycle Home > Now Playing > Current Playlist).  I would treat the 'Now Playing' button on old remotes similarly, except that the first screen to come up if you're not already in NP would be NP.

Are there any others?
Comment 4 Jim McAtee 2009-08-21 14:27:05 UTC
From a thread in the Fab4 forum regarding changes to be made to the production Fab4 remote, it looks like there will be a Now Playing button in addition to a Home button.  So that leaves only Brightness and Size, correct?

At r7210 the Brightness button still pushes into the Brightness adjustment screen and they still stack up if you press it more than once.
Comment 5 Ben Klaas 2009-08-26 07:50:07 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 6 Felix Mueller 2009-10-15 18:11:25 UTC
- Brightness button is fixed an does not stack windows anymore.

- Now Playing also works

- Size still needs fixing
Comment 7 Pat Ransil 2009-10-23 05:09:41 UTC
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Comment 8 Chris Owens 2010-03-08 11:33:06 UTC
Moving lower-priority bugs to next target
Comment 9 Jim McAtee 2010-04-25 14:07:39 UTC
(In reply to comment #6)

> - Brightness button is fixed an does not stack windows anymore.

The 'fix' here was to have the brightness button bring up the Settings > Screen > Brightness menu.  This is of very little use.  Please implement it so that it emulates the behavior of past ip3k players.  Have Brightness cycle through several different manual brightness levels:

100, 75, 50, 25, 0 

(or similar, but 0 needs to be included)

Currently, there's no easy way to manually change screen brightness.  Digging through the Touch's settings and using the slider is very tedious and time consuming.  Screen brightness on the Touch is as important as it was on previous players, but there's no simple remote control ability.

> - Size still needs fixing

Since there is no font sizing capability on the Touch, the only logical thing to do with Size is to switch between the two skins - Touch and Remote.  This needs to honor the text size settings in Screen > Select Skin.  If they're the same, ignore the button press.