Bug 3730 - Remember view mode in different contexts
: Remember view mode in different contexts
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 6.5b1
: PC Windows XP
: -- enhancement (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-11 13:04 UTC by Philip Meyer
Modified: 2011-11-06 23:22 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2006-07-11 13:04:53 UTC
It appears that the last selected view mode (list view or gallery view)
is remembered for all possible album display modes.  It would be nice
if the last used mode could be remembered in each context.

For example, I would like "Browse Albums" to remember its mode separately
from "Browse Artist -> Album".

Selecting an artist may result in a few albums, so browsing the artwork
is nice and I'd like to keep it in this mode.  However, I would use
Browse Albums by artwork much less frequently because I get many artwork
thumbnails (as you get a list of all albums for the chosen starting letter).

New Music can also display list/gallery mode, so perhaps this mode could be
rememebered separately from the other contexts too.
Comment 1 Philip Meyer 2006-07-11 13:07:41 UTC
KDF said:

if you wanted to remember different types, you could use the 'level' param.  
top level is 0, artist->albums is level 1. I'd add another param in 
Pages/BrowseDB for level to go alongside levelName (~line 500), add a 
check against the level param in Web/HTTP.pm around line 686 then edit 
the toggleGalleryView script in common.js to handle the ccookie for a 
given level (pass the %level% tt object as a second arg, as one option)

----

However, I believe that this would mean "Browse Albums" and "New Music"
would share the same mode setting.  The ultimate solution would make
each browse method remember its own list display mode.
Comment 2 Alan Young 2011-11-06 23:22:50 UTC
Unassigned bugs cannot have a priority.