UI Problem in Editor When Moving Files

[Jaws]

Context: On a laptop, Windows, using a trackpad pointing device.

Problem: When reordering an epub's files under the [text] segment -- such as moving the copyright page from the end to right after the title page, and similar for tables of contents -- for books with lots of individual HTML files under [text], it's quite difficult to smoothly move say, the 38th file in the [text] segment so it's the 3d file (putting the copyright page and the table of contents at the end, like some publishers do, is... annoyingly nonstandard behavior for a BOOK). Frequently, while trying to move that file all the way up with a drag-and-drop, the drag-and-drop goes PAST the first page if the first page isn't visible when starting the drag-and-drop, which collapses the [text] segment and aborts the move.

(My unpredictable hand/finger-shaking of early-stage Parkinson's doesn't help, but this has been a problem since Calibre 3.)

Suggested/possible solutions for a future enhancement, any of which would be a big help:
(a) Add "move to top" (and corresponding "move to bottom") options
(b) Enable use of arrow up/down keys to move
(c) Disable the "collapse this segment" behavior when a carried file moves on top of the segment label

[Karellen]

Originally Posted by Jaws

Frequently, while trying to move that file all the way up with a drag-and-drop, the drag-and-drop goes PAST the first page if the first page isn't visible when starting the drag-and-drop, which collapses the [text] segment and aborts the move.

Yes, this happens to me quite often as well. Suddenly the list has collapsed and my xhtml file has jumped back down to 97th position in the list. Sometimes it will happen two or three consecutive times before I can move it correctly.

Originally Posted by Jaws

Suggested/possible solutions for a future enhancement, any of which would be a big help:
(a) Add "move to top" (and corresponding "move to bottom") options
(b) Enable use of arrow up/down keys to move
(c) Disable the "collapse this segment" behavior when a carried file moves on top of the segment label

a) sounds reasonable
b) don't like. Potentially clicking the up arrow 30, 50 or 100 times will be frustrating
c) should be standard during move operations.

how about...
d) something like a line number, and you simply type in the number where the file should be moved to, and all following files are bumped by one to make room for the moved file. I imagine a context menu option - "Move to..." and a dialogue box to enter a number.

[BetterRed]

Originally Posted by Jaws

. . .
(My unpredictable hand/finger-shaking of early-stage Parkinson's doesn't help, but this has been a problem since Calibre 3.)

Ditto, but due to injury, and more recently, neuropathy.

My suggestion would be to add an option to the File browser context (right click) menu:

Move... -> Top
           Up
           Down
           Bottom

Perhaps with keyboard shortcuts, e.g. Ctrl+Home, Ctrl+↑, Ctrl+↓ and Ctrl+End - that repeat.

BR

[kovidgoyal]

https://github.com/kovidgoyal/calibr...d22c24d7a95760

[Karellen]

Thank you @kovidgoyal

[JSWolf]

Originally Posted by Jaws

(My unpredictable hand/finger-shaking of early-stage Parkinson's doesn't help, but this has been a problem since Calibre 3.)

You would be better off with a mouse or a trackball and not the trackpad.

[theducks]

Originally Posted by kovidgoyal

https://github.com/kovidgoyal/calibr...d22c24d7a95760

Anything you can do for the TOC edit (stand alone or in the Editor)
When trying to nest, sometimes it flips the order (6>1) instead of maintaining 1>6 when nested. I have not been able to identify the exact reason. It is a real PITA to manually reorder a dozen entries)

[kovidgoyal]

If you can come up with a way to reproduce the issue I will be happy to take a look.

[Jaws]

Originally Posted by kovidgoyal

https://github.com/kovidgoyal/calibr...d22c24d7a95760

This code and the described behavior of the code is exactly what is causing me trouble — I suppose I'm requesting something "less fiddly" (first segment line 139) or another solution like the ability/a clear setting to not cause segment collapse when the segment head is rolled over after moving from "off screen."

That latter is far from unique to Calibre — it's a rather default UI problem in this day of many programmers using multiple monster-sized screens for their work (and not then exhaustively testing on non-custom setups with more, umm, "consumer-grade" hardware). One can observe it in both Mac and Windows folder-moving operations, and I recall it in a 2017-vintage Linux graphical interface. So no blame, just a request concerning something that I've seen and as other comments indicate isn't unique...

[kovidgoyal]

Take it up with the developers of Qt, the widget toolkit calibre uses. The drag and drop behavior comes from there.

[Jaws]

Originally Posted by kovidgoyal

Take it up with the developers of Qt, the widget toolkit calibre uses. The drag and drop behavior comes from there.

OK, now I understand why you just linked to the code... and I certainly will. With no expectation whatsoever that I'll even get a response.

This is far from the only problem with Qt and its, well, obliviousness regarding anything even mildly outside the ordinary. (It's a years-long problem.) As I noted, though, this is also an OS-level problem — what in my first career would have been called an "attitude problem" corrected through some quality time with a senior NCO and perhaps a visit to the Old Man (me). Which I suppose makes me an old Old Man.

[DNSB]

Originally Posted by Jaws

OK, now I understand why you just linked to the code... and I certainly will. With no expectation whatsoever that I'll even get a response.

This is far from the only problem with Qt and its, well, obliviousness regarding anything even mildly outside the ordinary. (It's a years-long problem.)

That's probably one of the kindest phrases I seen used to describe the QT corporate/developers' attitude towards end user complaints.

[Jaws]

Originally Posted by DNSB

That's probably one of the kindest phrases I seen used to describe the QT corporate/developers' attitude towards end user complaints.

I'm not trying to be kind, just not-NSFW. I know how to deal with recalcitrant software vendors — all the way to "due to continued noncompliance, you are barred from bidding on government contracts for 5 years."