[wold]

Originally Posted by Savate

(i) the method requires one to first press the beginning (or end) of the text section, then drag the pointers to mark the text region, and then to choose to commit highlight from the popup menu bar.

Yes the current PB selection method is waaay clunkier. I kinda got used to it though. It will have to do (and supports PDFs as well).

On a Lux5 selecting text does feel slower on recent firmwares, which is perhaps what you are describing. Auto-selection has become smarter though w/r to including special characters at the end of a sentence (.?!, etc). That was always a pet peeve of mine

Removed seems to be selecting a whole paragraph, by dragging to the empty space at the end of that paragraph. It usually kicked in when unwanted, and when now wanted it skips to the line above or below

Next to Kindle, Kobo and Sony also use the touch and select-by-drag approach. It is more intuitive. With Sony being the lesser one (not auto-detecting word edges, ugh).

(ii) dragging the highlight pointers across a screen break is woefully difficult! almost impossible in most cases. I have decided that the only reliable approach is to highlight the first part on the first screen and then move to the next screen and highlight the next part.

Highlighting across screen breaks can be done (it seems to work better, but not much) if you start at the end of the section and highlight to the beginning - negotiating the screen break seems easier in that direction for some reason).

The simplest, but for me a clunky strategy, is to highlight one screen at a time. That works but where you hoped for one single section of highlighted text the downloadable notes display it as two highlights.

My current method is to make a selection on page #1, use the page buttons to flip to the next page - and reposition the end marker from topleft. Alternatively, there's drag to the bottom-right corner to flip, but that sometimes flipped multiple pages (IIRC this seems fixed).

BTW, neither Kobo nor Sony can do multipage selections. This kinda surprised me.

Having written all this, recently on my Lux5 selecting and dragging text hasn't been all that accurate. Not sure it's the unit (calibration) or a software problem.

And this stuff is complex to program: assume its javascript running in a HTML browser. With JS/C there are enough 'less-optimal' ways to do it (rebuilding regex objects for one ). There was someone here recently complaining about the older (=slow) processor/socs used in PBs.

As I said at the beginning, I wonder if this is because the screen size makes a difference. (...)

It can add to the problem. With screen PPI/resolution increasing there's ever more pixels to be rendered to the screen. Would you know I got the Lux5 over the HD3, for this very reason (and the SD card).