Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by Redrum
    Agree with The Groundsman and darrell . No long press needed. Always present all options** and cancel.

    ** all options differing if one or multiple tracks in queue as stated.
    Seems a bit pointless to present options that have no effect.

    Originally posted by Redrum
    My question would be - if multiple tracks are in the queue, and you select "remove previous tracks" would that launch another "confirm" dialog box? I am not sure that is necessary as long as the selections are separated enough to prevent a fat finger. But, if it is a two tap solution, no big deal.
    No, that'd be way too much! The dialog is a choice dialog (as per sleep options, DSTM, mutli-disc, etc.)

    Originally posted by Redrum
    Maybe an option to enable/disable two tap requirement, similarly a "remember this choice" or "don't ask again"
    Problem with those solutions is that you then need a way to re-enable the "don't ask again" questions.

    Material 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.

    Comment


    • Originally posted by cpd73

      Tried, but I think this looks weird:

      Click image for larger version

Name:	single-track.png
Views:	328
Size:	8.8 KB
ID:	1639700

      Maybe just lose the heading (in both cases) ?

      Comment


      • An idea for a related enhancement: how about "remove previous/following/all but this one" options in the track drop-down? (if this resulted in the currently playing track being removed, the selected track would play).

        Comment


        • Originally posted by cpd73

          Seems a bit pointless to present options that have no effect.
          I misspoke. I meant to say exactly what you had presented. I meant to say different options would be presented based on if there is one or more than one track. Sorry for the confusion.

          Also was not advocating an additional confirm, just asking. To me, too many confirms are annoying, unless unintended actions have unrecoverable consequences (e.g. "format drive?")

          Jim

          Comment


          • Originally posted by darrell

            Maybe just lose the heading (in both cases) ?
            Would be even worse, as the main text would look like just text and not a button
            Material 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.

            Comment


            • Originally posted by cpd73

              Would be even worse, as the main text would look like just text and not a button
              Radio buttons? But it's fine as you have it.

              Comment


              • Originally posted by darrell

                Radio buttons? But it's fine as you have it.
                Radio buttons do not activate an action when pressed. So you would need radios and an ok button. Plus in the instance we are talking about there would be only 1 radio, which would look silly
                Material 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.

                Comment


                • Originally posted by cpd73

                  Radio buttons do not activate an action when pressed. So you would need radios and an ok button. Plus in the instance we are talking about there would be only 1 radio, which would look silly
                  Final idea (I'm not arguing with you, just chucking ideas about - as I said, you proposal is fine:

                  put cancel in the list instead of a blue button.

                  Anyway, what did you think of the track drop down idea, above?

                  Comment


                  • Across the years of the development of this much-appreciated interface, there have been a few questions about the screensaver. I'd like to add my voice to request some more options here, not least because there are still screens that get burn-in. The option to have the clock text move around the screen every so often, for instance, would be useful. Or at least being able to control the brightness of the clock?

                    Comment


                    • Originally posted by darrell
                      put cancel in the list instead of a blue button.
                      Again, no - its too inconsistent. I'm pondering with the idea of always showing all options, but dimming out the inactive ones. This way it still looks like a list.

                      Originally posted by darrell
                      Anyway, what did you think of the track drop down idea, above?
                      Too many items in menu as is, so don't really want to add more.
                      Material 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.

                      Comment


                      • as another option, just an idea~

                        Remove All Tracks
                        Remove Select Tracks (grayed if only a single track). When selected:

                        ----> Remove Upcoming Tracks
                        ----> Remove Preceding Tracks

                        The thought being it's the same screen for one or more tracks in the queue, but the option for removing pre/up is grayed if there is only one. Remove Select (or whatever you want to call it) pulls a second menu to complete the operation.

                        It's a two level solution for the "custom" operation, but you could argue the extra clicks are's a big deal, because the majority case is the clear the entire queue, the special case it to remove before or after tracks. The main + is the remove queu screen is the same, just grayed if only one. It will help remind the users (us) that this function is available.

                        Jim

                        Comment


                        • Originally posted by cpd73

                          [Edit] After playing with this for a while now, I'm leaning towards having the more complex dialog via long-press, as when I press clear I want to remove all tracks...
                          The proposed function is very welcome here, I do from time to time need to go back and delete identical tracks. Re the long press, I am a great one for forgetting about long presses in situations where I am not doing it very frequently, comes with age! Having said that< I am a fan of log press selection, how about building both in, short brings up menu, long deletes duplicates. Just to complicate it! :-)
                          Serverrpi3 pCP8.1.0 LMS8.2.0
                          MediaUSB hard drive
                          Lounge/dining areasSBT > Denon AVR2113 > Bose Acoustimass10 / Krix Seismix3 18" 300w RMS custom cinema sub (& AR 77XB t/table, Stanton 680MkII / Grado F-1+ > NAD7155 to phono pre-amp > Amp+)
                          Family/kitchenSBT > Denon AVRX3000 zone 1 > Krix Acoustix F, Centrix C, Holographix R & Original Seismix 7 15" 400w RMS sub
                          AlfrescoZ2 > Krix Tropix/Klipsch SW
                          OthersSB Player/androids > Bose Soundlink Mini
                          SBT/SB Player Remotes Squeeze Ctrl/androids

                          Comment


                          • Originally posted by DavidBulluss
                            short brings up menu, long deletes duplicates
                            Hmmm... not to keen on that. I have settled for always showing all options, and greying out unusable options - that way the action is consistent.

                            For the next release, however, I've also just added 'Remove duplicates' to the queue's 'Action' menu,
                            Material 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.

                            Comment


                            • 3.3.0 release, changes:

                              1. Material-3 like bottom navigation bar for mobile layout.
                              2. Material-3 like switches.
                              3. More rounded dialogs.
                              4. Remove shadows from dialogs, volume popup, and menus.
                              5. Less rounded chips.
                              6. Add 'Kiosk' mode; hide all main menu items (except custom actions), and allow configuring which actions are available.
                              7. Refactor volume handling to throttle volume change requests.
                              8. Better layout of now playing when using very wide views.
                              9. If sorting of favourites is enabled, then also sort 'Radio / My Presets'
                              10. Add some missing shortcut in tooltips.
                              11. Fix 'Esc' closing dialog and then parent dialog.
                              12. Better duplicate 'time' fix.
                              13. Strip HTML tags for browse item tooltips.
                              14. Handle text items (max 2 lines) when showing over 100 items in a list.
                              15. Only show total library duration if there are tracks in library.
                              16. Only show library last update date if valid.
                              17. Don't remove icons in favourites just because they are all the same.
                              18. Fix 'Play next' when invoked from header of multi-disc album.
                              20. When prompting to clear queue ask if all tracks, upcoming, or previous should be removed.
                              21. Disable context menu (long-press) for items on mobile devices.
                              22. Dim screensaver text.
                              23. Move screensaver text position to random location every 10 minutes.
                              24. Add 'Remove duplicates' to queue 'Actions' menu.

                              Material 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.

                              Comment


                              • Originally posted by cpd73

                                Hmmm... not to keen on that. I have settled for always showing all options, and greying out unusable options - that way the action is consistent.

                                For the next release, however, I've also just added 'Remove duplicates' to the queue's 'Action' menu,
                                I wonder if it would be better for the option "remove previous tracks" to be renamed "remove played tracks"? There isn't an explicit reference point for "previous".

                                Comment

                                Working...
                                X
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎