Bug 12514 - Default Wallpaper for baby should be Encore Red
: Default Wallpaper for baby should be Encore Red
Status: RESOLVED FIXED
Product: SB Radio
Classification: Unclassified
Component: Setup
: Include FW version in comment
: PC Windows Vista
: P1 normal (vote)
: MPQ
Assigned To: Wadzinski Tom
:
Depends on: 12418
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-23 18:28 UTC by ndijulio
Modified: 2009-09-08 09:19 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ndijulio 2009-06-23 18:28:10 UTC
Current Default is set to Black...
Comment 1 Blackketter Dean 2009-06-23 19:38:57 UTC
Actually, the red model should use Encore Red and the black Nocturne.
Comment 2 ndijulio 2009-06-23 20:14:38 UTC
For setup why would you want to see Encore Red?  Don't you think this will be distracting?
Comment 3 ndijulio 2009-06-26 10:21:55 UTC
Default wallpaper for setup and UI

black plastic - Encore

red plastic - Encore Red
Comment 4 Ben Klaas 2009-06-30 09:23:37 UTC
mine to fix for MPQ
Comment 5 Ben Klaas 2009-07-02 09:12:39 UTC
default is bb_encore.png now for all babies. When I can identify a baby as being red or black, I can switch red ones to using bb_encore_red.png
Comment 6 Jim McAtee 2009-07-02 10:45:43 UTC
IMO, setup wallpaper should always be Black. Change it after setup.
Comment 7 Chris Owens 2009-07-07 10:15:03 UTC
This bug has been identified as one that may not be required for MPQ since it now seems clear that MPQ and MP firmwares will be different.  Please comment if you disagree with this assessment.  Thanks!
Comment 8 Ben Klaas 2009-07-07 18:04:06 UTC
to Richard for comment:

will we have a means via software for querying red or black baby boom before MP? If so, target for MP. If not, this can target for 7.4.

assign back to me after comment...
Comment 9 James Richardson 2009-07-08 10:28:08 UTC
Tom: David needs to check in fix for bug 12418 first, please call Richard to get further instruction on this bug.
Comment 10 Wadzinski Tom 2009-07-09 14:23:53 UTC
fixed in r6477