Results 6,711 to 6,720 of 7114
Thread: Announce: Material Skin
-
2021-03-02, 13:08 #6711
- Join Date
- Jan 2013
- Posts
- 313
-
2021-03-02, 16:09 #6712
I don't understand how having to open the top-level menu, click on "Information", and then click on "Server Settings" or scroll down and click on "Player Settings" can be quicker than if all the "Settings" options were still just listed in the top-level menu — i.e. it's now 3 clicks for Server or Player Settings, compared with just 2 clicks in the "old approach".
(That said, accessing the Settings menus via "Information" is certainly easier than having to multiply scroll/swipe to the bottom of the interface Settings page to click on them.)Last edited by SpiderJon; 2021-03-02 at 16:12.
Duet x 3, via various hi-fi. LMS on Raspberry Pi OS (Debian 10) on a Pi4.
-
2021-03-03, 00:14 #6713
- Join Date
- Feb 2020
- Location
- Seattle
- Posts
- 115
-
2021-03-03, 00:52 #6714
- Join Date
- Mar 2017
- Posts
- 2,738
Oh, wow! 1 extra click...
You don't have to, the settings are accessible from the settings dialog's menu - as stated in the release anouncement.
.......................
I have been ignoring this conversation up until now, but its getting silly. I do not intend to re-add the items to the main menu:
a) Having (if you use the APK) 4 settings entries in one menu is silly - most other systems have 1 settings entry
b) Some have complained that the meannig of each was not clear - hence why in the settings dialog, below the relevant settings button, there is now some help text
c) For 2.3.2 I'm adding icon-buttons in the settings dialog's toolbar to access application, player, and server settings (if there is space) - so now its open menu, click settings, click app/player/server button
d) Material Skin is mobile focused, in this layout there is more than 2 entries (Settings, Information) in the menu - as some of the browse, or queue, items are placed into the menu because of size constraints. With these and 3 superflous settings entries it was getting crowdedMaterial debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
2021-03-03, 01:57 #6715
- Join Date
- Jan 2013
- Posts
- 313
-
2021-03-03, 02:09 #6716
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 6,580
-
2021-03-03, 02:33 #6717
Well, yes. I get your sarcasm*, but the point was that 3>2, which can't be "quicker" or "more convenient" — just that, and nothing more than that.
* that isn't sarcasm. I realise 1 extra click is essentially trivial, but it's mildly irksome at times when you need to repeatedly access the Server settings for some reason or other.
You don't have to, the settings are accessible from the settings dialog's menu - as stated in the release anouncement.
Again, thanks for all the work you've done on Material Skin. It's a great achievement.Duet x 3, via various hi-fi. LMS on Raspberry Pi OS (Debian 10) on a Pi4.
-
2021-03-03, 08:09 #6718
- Join Date
- Nov 2020
- Location
- Ireland
- Posts
- 16
Add to Playlist
Thanks for the 'add to playlist' from queue feature, it's a great one for me. And thank you again for all your hard work on Material Skin, it's getting better all the time.
-
2021-03-03, 11:00 #6719
- Join Date
- Jul 2020
- Posts
- 261
The Material menu can also be customised to meet your specific needs. When I was new to LMS I also had to access the server settings all the time, and added a menu item for "server settings classic" in the actions.js, as outlined here: https://github.com/CDrummond/lms-mat...ed-Information
(Note to self: Now that I'm done tweaking I never use this anymore, so may as well remove it)
-
2021-03-03, 12:00 #6720