Is there a reason why the Controller interface has decided to show a mixer even though it will never be available on that type of object ?
As an example, lets say the Dynamic Playlist plugin decides to only implement mixers on albums. In this case the Controller interface shows the Dynamic Playlist mixer also on artists, genres and tracks but when the user selects it, he gets an error message that the mixer isn't available on this item. This is different behavior from the PlayerUI which only shows mixers that are available on the selected item. The web interface is consistent with the PlayerUI and only displays mixer buttons for the mixers that are available. Is there a reason why the Controller interface has a different behaviour than the PlayerUI and WebUI ? My feeling is that the different interfaces should have a consistent behavior, so assuming this is the common feeling, which interface behaves correctly ? -- erland Erland Isaksson 'My homepage' (http://erland.isaksson.info) 'My download page' (http://erland.isaksson.info/download) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library and Database Query plugins' (http://wiki.erland.isaksson.info/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=50744 _______________________________________________ jive mailing list [email protected] http://lists.slimdevices.com/cgi-bin/mailman/listinfo/jive
