Bug 3548 – Cycle through menu by pressing the Search/Browse buttons

Bug 3548 - Cycle through menu by pressing the Search/Browse buttons

Summary:

Cycle through menu by pressing the Search/Browse buttons

Status:	CLOSED FIXED

Product:	SB Transporter
Classification:	Unclassified
Component:	SB Server
Version:	unspecified
Platform:	PC Other

Importance:	P2 enhancement (vote)
Target Milestone:	Future
Assigned To:	KDF

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-06-14 04:51 UTC by Richard Titmuss
Modified:	2008-12-15 13:04 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
step through browse/search on repeat presses (1.18 KB, patch) 2006-08-18 00:07 UTC, KDF	Details \| Diff
View All 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 Richard Titmuss 2006-06-14 04:51:52 UTC

I keep finding myself trying to cycle through the options on the top level Search and Browse menus by repeatedly pressing Search or Browse buttons. e.g. Search should cycle through Artists > Albums > Songs > Artists > etc.

I sometimes do this on the remote too, but I seem to be doing it more frequently with the front panel buttons.

Comment 1 Dan Sully 2006-08-11 14:29:52 UTC

Who should this belong to?

Thanks

Comment 2 KDF 2006-08-18 00:07:13 UTC

Created attachment 1442 [details]
step through browse/search on repeat presses

checks for INPUT.List mode and the menu position to determine if the search/browse buttons are being used from within their sections of the menus, then uses the INPUT.List 'down' function to step through the menus lists.

Comment 3 Blackketter Dean 2007-10-22 17:09:08 UTC

Heh, I never saw this patch.  I like it.

Comment 4 KDF 2007-10-22 19:21:09 UTC

merged to trunk at change 14028

Comment 5 James Richardson 2008-12-15 13:04:34 UTC

This bug appears to have been fixed in the latest release!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Make sure to include the version number of the software you are seeing the error with.