TL;DR: When fixing, please keep in mind that this is two separate issues (not counting @skoobeâs multi-file-drag issue):
- Obs interprets some clicks from over-sensitive HIDs (pen+tablets, some mice) as drags; these âdrag-clicksâ do not result in the file opening as expected, causing frustration.
- A bug causes dragged files (and folders), released within the same folder, to moved up one level in the folder hierarchy, causing frustration.
Issue #1 triggers #2, but only fixing #2 makes #1 only slightly less frustrating. Please treat as separate issues, and please fix both.
Just to weigh in with my experiences â I also have this problem, and, like @digross, I use a Wacom tablet (specifically Cintiq 16") instead of a mouse.
Iâve also had this problem (just the drag-instead-of-click part, not the hierarchy jump issue) with other software in the past, specifically in a Wacom / pen+tablet HID context, and the issue seems to be that youâre more likely to move the pen tip while clicking on a file (which translates as a left click + drag, if not accounted for) when using pen+tablet than you are with a mouse (depending on the sensitivity and type of the mouse, of course, as seen in this thread).
The few times where I have managed to get the relevant Devs to fix the issue, the solution is to implement some sort of [distance moved (in pixels) before triggering âdragâ] in the appâs code.
I agree with @WhiteNoise that this is related to the other issue, and with @umami that the expected behavior for initiating a drag, and then dropping the file âon itselfâ (where it already was), or into the folder it is already located in, is that the drag action should be cancelled.
I did some further testing with a file nested in five layers of subfolders, and even if you drop the file on the folder already containing it (current folder), the file still gets moved up one level (and always just the one level) in the hierarchy (parent of current folder), even if the tooltip says â[filename] - move into [current folder name]â when drag-hovering over the file itself, or anywhere else in the containing folder (or on the containing folderâs title).
Apart from pressing ESC (not a thing when you were just trying to click, not drag), there really is no way to avoid moving the file up one level.
Since the main issue here seems to be that âdrag file to its current containing folderâ is broken (which, incidentally, is triggered for some of us because of pen/tablet use or over-sensitive mice), I suspect that this issue can be partially corrected by implementing/fixing [cancel move action if file is dragged to its current containing folder].
However, when implementing the fix, please keep in mind that the over-sensitiveness of the drag function, combined with the move-up-one-level-in-the-hierarchy bug, is not the only issue.
Even if the hierarchy bug is fixed by [cancel move if destination same as current location], everyone who was affected by it will still experience drag-instead-of-click (just without the hierarchy bug, hopefully). Since the drag option does not open the file in question (at least in my tests), we will still experience clicks that donât always open a file (because Obs thinks weâre dragging it, not clicking it), which is frustrating.
As such, please look into some sort of [only trigger âdragâ after cursor has moved X pixels] solution in addition to fixing the hierarchy bug. A suggestion would be 3-10 px, but less might do it.
Granted, this will lead to dragging feeling the tiniest bit âstickyâ, which some might find annoying. A compromise would be to have the âdrag delayâ fix as a (default: off) option in Settings, probably in the Editor â Advanced tab/section.
If youâre feeling really fancy, the distance-in-pixels-before-drag-triggered value could be user-defined, resulting in this hypothetical setting:
Settings â Editor â Advanced:
File & folder drag delay
Requires dragging a file or folder a few pixels before the actual drag action is initiated; prevents clicks from certain HIDs (pen+tablets, very sensitive mice, etc.) from being interpreted as drag actions.
Default amount (3 px)
Custom amount
Number of pixels before drag action is initiated: ___ px
- Add standard toggle to enable/disable setting, default âoffâ.
- Options (Default/Custom) grayed out when toggle is âoffâ.
- âNumber of pixels âŚâ + text field grayed out when Default is selected.
I hope the âdrag delayâ can be implemented, even if the extra Setting is a bit out of scope. Either way, Iâm looking forward to the hierarchy bug hopefully being fixed in 1.5.4!