Bug 118095 - Provide an option to disable drag and drop editing
Summary: Provide an option to disable drag and drop editing
Status: RESOLVED DUPLICATE of bug 100998
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.4.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-10 10:45 UTC by lvm
Modified: 2018-11-07 11:19 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lvm 2018-06-10 10:45:10 UTC
Description:
Provide an option to disable drag and drop editing for both writer and calc, in this mode click and hold on selected area should start a new selection instead of moving the existing selection.

Steps to Reproduce:
see description

Actual Results:  
see description

Expected Results:
see description


Reproducible: Always


User Profile Reset: No



Additional Info:
is it possible to have one bug for both writer and calc or should I create two?


User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3
Comment 1 Regina Henschel 2018-06-21 18:59:05 UTC
You select a text and the next mouse-down on it will deselect it? How will you then drag something?
Currently you click on the selected text, which will deselect it, and then click with mouse-down starts a new selection. What is bad with that workflow?
Comment 2 Heiko Tietze 2018-06-22 08:02:46 UTC
I understand the request to be 'always in select mode' as a way to never move selections for safety reasons. But that's not common neither needed as a single click un-select. 

Feel free to reopen and state a more clear use case like "I want to do <foo> because <bar> is not possible" and we find a solution.
Comment 3 lvm 2018-06-23 09:10:29 UTC
Suppose I want to select some text with a mouse. What I want is to just do it - press a button and move - done. If I understand you correctly you are proposing that I should
1. consider whether the new selection starts in the middle of the existing one
2. if yes, make a second click - and wait, because if I click the second time immediately it will be treated as a doubleclick making a new selection, and here we go again, or click somewhere else
3. after a pause, start a new selection

There is nothing complex there, but editing a text is a set of automatic actions when you don't think at all - like you don't think when you are walking 'I should lift my left leg and place it here', you just do it without thinking. What you are proposing breaks this automatism, and this is an awful UX. I can only restate that I want an option to completely disable drag and drop. I am quite sure that I will never want to use it and it causes a number of unwanted side effects described above. In this mode clicking on the selected area should cancel the previous selection and start a new one from the point of the click.

I also may add that when I found no way to disable the drag and drop I tried googling for the solution before filing this bug but found only pages and pages of people lamenting the absence of this feature. You should try it too before stating that there is no need for it. https://www.google.co.uk/search?hl=en&ie=utf-8&q=libreoffice+disable+drag%27n%27drop&btnG=Google+Search&gws_rd=ssl
Comment 4 Heiko Tietze 2018-06-23 09:16:56 UTC
(In reply to lvm from comment #3)
> ... you are proposing that I should 1. consider whether the new 
> selection starts in the middle of the existing one...

That's how it works in all programs. The only exception I know is Okular, KDE's PDF viewer, and graphic tools, of course. Still WF.
Comment 5 lvm 2018-06-23 10:18:55 UTC
If you think that going with the flow is the correct choice then you must realise that vast majority considers MS office as the standard, and it quite wisely provides an option to disable drag and drop. It is a feature more for occasional users.
Comment 6 Xisco Faulí 2018-11-07 11:19:35 UTC
I guess we can close this one as a dupe of bug 100998

*** This bug has been marked as a duplicate of bug 100998 ***