Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accidental mouse drag deselects too easily #17360

Open
reaperrr opened this issue Nov 20, 2019 · 6 comments
Open

Accidental mouse drag deselects too easily #17360

reaperrr opened this issue Nov 20, 2019 · 6 comments

Comments

@reaperrr
Copy link
Contributor

reaperrr commented Nov 20, 2019

From ModDB comments:

"I still have occasional problems with issuing commands.
If I want to click to send a unit to go/attack something somewhere, and I hold the click a few milliseconds too long while moving at all, it drags a tiny box instead, and my units are unselected.
It should behave like this:
if you have units selected, dragging a box of less than a given area, simply sends your units to the origin point of the box."

FWIW, now that it's been pointed out, I've had that issue a few times myself, the way it currently works is definitely not optimal. Treating it as normal click if the mouse has been moved less than n (~5?) pixels sounds like a possible solution.

@tovl
Copy link
Contributor

tovl commented Nov 20, 2019

We already do this! There is a 24 pixel deadzone on unit selection boxes in OpenRA which is the width of an entire cell. I think making it even larger would hinder the functionality of drag selecting. Also, it seems the originals had a much smaller deadzone—more in the order of the 5 pixels you suggest (and yeah, I've found it to be an annoying problem in the originals, but not so much in OpenRA).

The most that we can do here is maybe to expose the deadzone size to the settings menu, but that is about it. Otherwise I would suggest lowering your mouse sensitivity if your find that this happens often.

A more comprehensive solution might be to use a different mouse button for giving orders than we use for selecting. 😉

@reaperrr
Copy link
Contributor Author

We already do this!

Whoops...

A more comprehensive solution might be to use a different mouse button for giving orders than we use for selecting.

That sounds like an idea worth trying to me.

In case that gets rejected for some reason, (slightly) increasing the milliseconds the mouse button needs to be pressed before it registers as dragging would be the only other alternative solution I can think of.

@pchote
Copy link
Member

pchote commented Nov 20, 2019

A more comprehensive solution might be to use a different mouse button for giving orders than we use for selecting.

This was a subtle hint that players should stick with the right click orders instead of switching to the classic left click 😉

@reaperrr
Copy link
Contributor Author

I guess it shows that I don't actually play much...

@PunkPun
Copy link
Member

PunkPun commented Nov 21, 2019

Having high mouse sensitivity is detrimental to all rts's, OpenRA is no exception. He should simply reduce it.

@deleted-user-1
Copy link
Contributor

(slightly) increasing the milliseconds the mouse button needs to be pressed before it registers as dragging would be the only other alternative solution I can think of.

This might still be a good idea in addition to the existing deadzone setting and might solve the problem for people with high mouse sensitivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants