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

Option to disable double-clicking to select grid #1901

KashouC opened this Issue Oct 16, 2018 · 3 comments


None yet
2 participants

KashouC commented Oct 16, 2018

Haven't had much of an issue with this before, but double clicking happens too easily with a tablet and I accidentally select the grid all the time now and it's not something that I use a lot.

Aseprite 1.2.10-beta1
Windows 7

@dacap dacap self-assigned this Oct 16, 2018

@dacap dacap added this to the v1.2 milestone Oct 16, 2018


This comment has been minimized.


dacap commented Oct 16, 2018

Some other users find the double-click hard to execute:

I think the issues is this: it's hard to trigger when one want to execute it, and too easy to trigger when one doesn't want, basically, it has an erratic behavior.

I'm not sure if we need a way to disable the double-click to select a grid cell, or a way to disable it completely in the editor, and create an alternative way to trigger the double-click action (e.g. with a key or an on-screen button)


This comment has been minimized.

KashouC commented Oct 16, 2018

It's strange. I think I'm getting better at it now but for a long time I had severe issues double clicking in menu's in Aseprite with the pen, it just wouldn't register, but getting the double click to work for the grid selection thing is way too easy (like an entire seconds window almost).


This comment has been minimized.

KashouC commented Oct 16, 2018

Could you perhaps link the timeout to the OS double click timeout so it's the same timing as opening files and such? Not sure how much of a hassle that is cross platform (I assume it is, usually is). But I dunno if that's the issue either so 🤷‍♀️

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