Bug 15337 – Pandora: After creating a station, UI should go straight to the now playing screen.

Bug 15337 - Pandora: After creating a station, UI should go straight to the now playing screen.

Summary:

Pandora: After creating a station, UI should go straight to the now playing s...

Status:	CLOSED FIXED

Product:	SB Touch
Classification:	Unclassified
Component:	App Gallery
Version:	unspecified
Platform:	PC Other

Importance:	P1 normal (vote)
Target Milestone:	7.5.0
Assigned To:	Michael Herger

URL:
Keywords:	partner_important

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-12-18 15:01 UTC by Vic Wong
Modified:	2010-04-08 17:24 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

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 Vic Wong 2009-12-18 15:01:46 UTC

After I create a station, I get a station list with one item: the new station. The station starts playing, but when I enter context menu and select "play this station" I get a blank screen that is labeled "Play this station". 

After creating a station it should go straight to the now playing screen.

Comment 1 Chris Owens 2010-01-08 09:56:00 UTC

Changed summary

Comment 2 Chris Owens 2010-01-14 11:22:23 UTC

It's probably most elegant to just jump to the now playing, and play the music.

Pandora notes that it can be confusing to be on the station screen, and the back menus are even more confusing.  Maybe at least have a cue that you should hit play to play.

Comment 3 Mickey Gee 2010-02-04 16:31:37 UTC

Michael: Can you provide suggestion about next steps?

Comment 4 Michael Herger 2010-02-04 23:08:17 UTC

I'm still waiting for my IP address to be whitelisted (Carl should be back next week). Can't do any Pandora work without that change.

Comment 5 Michael Herger 2010-02-10 06:40:12 UTC

change 7369 - when creating a station, jump directly to Now Playing

Comment 6 Chris Owens 2010-04-08 17:24:40 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!