Bug 16045 – Switching between close and far ui can be messy

Bug 16045 - Switching between close and far ui can be messy

Summary:

Switching between close and far ui can be messy

Status:	CLOSED FIXED

Product:	SB Touch
Classification:	Unclassified
Component:	UI
Version:	7.5.0
Platform:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	7.5.x
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-04-12 08:44 UTC by Spies Steven
Modified:	2010-09-13 11:59 UTC (History)
CC List:	1 user (show)

See Also:
Category:	Bug

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Spies Steven 2010-04-12 08:44:29 UTC

Sometimes on touch automatic switching between the close and far ui by using the ir remote can lead to a screen that is illegible.

On example to reproduce:

With a factory reset fab4 walk through setup using touch until you are at the screen where you can choose to use an existing account or create a new one.  Instead of using touch at this point use the ir remote to select.  Notice that the screen becomes garbled and hard to read.

I believe this is a duplicate but I have not found the original.

Comment 1 Ben Klaas 2010-04-12 08:52:22 UTC

My recollection is that we had disallowed skin switching through setup. If my memory is correct, that's the bug to fix. IR remote should be operational, but skin switching should not happen during setup.

Comment 2 Chris Owens 2010-04-12 09:27:12 UTC

Ben notes that at the Touch UI design time, he and Noah agreed that the the skin switching should be disabled due to lots of text needing to be on the screen.

Comment 3 Chris Owens 2010-04-12 09:44:33 UTC

Chris to add a test case for production FW qualification

Comment 4 Chris Owens 2010-09-13 11:59:41 UTC

This bug has now been fixed in a released version of the Squeezeplay firmware (SB Touch, SB Radio, and SB Controller).  If you are still seeing this bug, please make certain you are running firmware 9009 or higher, and re-open it.

Thanks!