Bug 3813 – Multiple presses of Browse button confuses menu

Bug 3813 - Multiple presses of Browse button confuses menu

Summary:

Multiple presses of Browse button confuses menu

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Player UI
Version:	6.5b1
Platform:	PC Windows (legacy)

Importance:	P2 major (vote)
Target Milestone:	---
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-07-25 13:14 UTC by KDF
Modified:	2008-09-15 14:39 UTC (History)
CC List:	0 users

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 KDF 2006-07-25 13:14:35 UTC

If you press BROWSE several times in a row, the menu system gets confused and cannot go LEFT out of the mode.  Realisticly, the sucessive presses should do nothing if already at the top level browse, and return to the top if already browsing.  Search simply detects if already in search mode, but browse uses INPUT.List so we cannot detect in the same way.

Have tried looking at menudepth, but this wouldn't let the button work once browsing lower hierarchies.

Comment 1 KDF 2006-07-25 13:48:18 UTC

note for later...
need to add
Slim::Buttons::Common::setMode($client, 'home');

before the jumpToMenu

Comment 2 Chris Owens 2006-07-25 14:27:08 UTC

It looks like you know what you mean, but I can't quite figure it out.  My remote doesn't even have a BROWSE button!

Comment 3 KDF 2006-07-25 14:32:44 UTC

sorry Chris.  I'm working with softsqueeze after the transporter merge. The remote has a browse button. I was involved in a bit of a code fix earlier to make the function work, but until recently have never tested it with a "real" buttons.

Comment 4 KDF 2006-07-25 19:52:27 UTC

fixed in change 8671