Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-1782

Allow locking table headers to prevent accidental resorting

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.5.0b1
    • 2.3.1
    • User Interface
    • None
    • Windows

      I've had this issue as long as I've been using Picard: it is WAY too easy to accidentally click the "title" heading on the right panel and resort the releases by title instead of artist (or anything else). If I'm working in alphabetical order, top down (which I expect is pretty common), I'm frequently trying to select the top release and click the header instead. If there were a setting to lock the order, or sort from a right click menu instead, that would be really helpful.

          [PICARD-1782] Allow locking table headers to prevent accidental resorting

          GitHub Bot added a comment -

          See code changes in pull request #1643 submitted by phw.

          GitHub Bot added a comment - See code changes in pull request #1643 submitted by phw .

          Psychoadept added a comment -

          Sounds good to me!

          Psychoadept added a comment - Sounds good to me!

          Philipp Wolfer added a comment -

          The locking of the header sounds useful. A checkable option on the header's context menu should do. When enabled it would prevent sorting, reordering and resizing the columns. It's a bit like e.g. the Windows taskbar can be fixated.

           

          Does this make sense? Would this solve your issue?

          Philipp Wolfer added a comment - The locking of the header sounds useful. A checkable option on the header's context menu should do. When enabled it would prevent sorting, reordering and resizing the columns. It's a bit like e.g. the Windows taskbar can be fixated.   Does this make sense? Would this solve your issue?

            outsidecontext Philipp Wolfer
            psychoadept Psychoadept
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2.5.0b1