Is it possible to suppress single-click events during a double-click?
Our application supports single click and double-click events on a window which do different things. However we always get a single-click event during the double-click which causes undesired effects.
Our application is in Qt but really this is a question about underlying Windows/Mac APIs - is this a fundamental detail that the OS detects a single click as soon as you lift your finger since it can't possibly know you are going to click a second time, or can it be prevented?
If it can't be prevented, is their an accepted best practice how to handle it?
macos qt winapi
add a comment |
Our application supports single click and double-click events on a window which do different things. However we always get a single-click event during the double-click which causes undesired effects.
Our application is in Qt but really this is a question about underlying Windows/Mac APIs - is this a fundamental detail that the OS detects a single click as soon as you lift your finger since it can't possibly know you are going to click a second time, or can it be prevented?
If it can't be prevented, is their an accepted best practice how to handle it?
macos qt winapi
1
The behavior cannot be changed. The common approach to deal with this is a user interface design, where the single-click operation doesn't interfere with the double-click operation. E.g. in Explorer, a single-click selects an item, whereas a double-click invokes the default operation on the selected item.
– IInspectable
Nov 21 '18 at 15:50
add a comment |
Our application supports single click and double-click events on a window which do different things. However we always get a single-click event during the double-click which causes undesired effects.
Our application is in Qt but really this is a question about underlying Windows/Mac APIs - is this a fundamental detail that the OS detects a single click as soon as you lift your finger since it can't possibly know you are going to click a second time, or can it be prevented?
If it can't be prevented, is their an accepted best practice how to handle it?
macos qt winapi
Our application supports single click and double-click events on a window which do different things. However we always get a single-click event during the double-click which causes undesired effects.
Our application is in Qt but really this is a question about underlying Windows/Mac APIs - is this a fundamental detail that the OS detects a single click as soon as you lift your finger since it can't possibly know you are going to click a second time, or can it be prevented?
If it can't be prevented, is their an accepted best practice how to handle it?
macos qt winapi
macos qt winapi
asked Nov 21 '18 at 14:06
Mr. Boy
21.8k69238458
21.8k69238458
1
The behavior cannot be changed. The common approach to deal with this is a user interface design, where the single-click operation doesn't interfere with the double-click operation. E.g. in Explorer, a single-click selects an item, whereas a double-click invokes the default operation on the selected item.
– IInspectable
Nov 21 '18 at 15:50
add a comment |
1
The behavior cannot be changed. The common approach to deal with this is a user interface design, where the single-click operation doesn't interfere with the double-click operation. E.g. in Explorer, a single-click selects an item, whereas a double-click invokes the default operation on the selected item.
– IInspectable
Nov 21 '18 at 15:50
1
1
The behavior cannot be changed. The common approach to deal with this is a user interface design, where the single-click operation doesn't interfere with the double-click operation. E.g. in Explorer, a single-click selects an item, whereas a double-click invokes the default operation on the selected item.
– IInspectable
Nov 21 '18 at 15:50
The behavior cannot be changed. The common approach to deal with this is a user interface design, where the single-click operation doesn't interfere with the double-click operation. E.g. in Explorer, a single-click selects an item, whereas a double-click invokes the default operation on the selected item.
– IInspectable
Nov 21 '18 at 15:50
add a comment |
1 Answer
1
active
oldest
votes
Start a timer when you get WM_LBUTTONDOWN
(or Qt equivalent). If you get WM_LBUTTONDBLCLK
(or Qt equivalent) before the timer expires, cancel the timer and execute your double-click action. Otherwise, when the timer expires, execute your single-click event.
On Windows, you can get the double-click time using GetDoubleClickTime()
.
That's about the best you can do - you can't prevent the single click message being generated in the first place on either platform.
WM_LBUTTONDOWN
,WM_LBUTTONDBLCLK
? I would preferQt::MouseButton
constants for this. ;-)
– Scheff
Nov 21 '18 at 15:22
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413864%2fis-it-possible-to-suppress-single-click-events-during-a-double-click%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Start a timer when you get WM_LBUTTONDOWN
(or Qt equivalent). If you get WM_LBUTTONDBLCLK
(or Qt equivalent) before the timer expires, cancel the timer and execute your double-click action. Otherwise, when the timer expires, execute your single-click event.
On Windows, you can get the double-click time using GetDoubleClickTime()
.
That's about the best you can do - you can't prevent the single click message being generated in the first place on either platform.
WM_LBUTTONDOWN
,WM_LBUTTONDBLCLK
? I would preferQt::MouseButton
constants for this. ;-)
– Scheff
Nov 21 '18 at 15:22
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
add a comment |
Start a timer when you get WM_LBUTTONDOWN
(or Qt equivalent). If you get WM_LBUTTONDBLCLK
(or Qt equivalent) before the timer expires, cancel the timer and execute your double-click action. Otherwise, when the timer expires, execute your single-click event.
On Windows, you can get the double-click time using GetDoubleClickTime()
.
That's about the best you can do - you can't prevent the single click message being generated in the first place on either platform.
WM_LBUTTONDOWN
,WM_LBUTTONDBLCLK
? I would preferQt::MouseButton
constants for this. ;-)
– Scheff
Nov 21 '18 at 15:22
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
add a comment |
Start a timer when you get WM_LBUTTONDOWN
(or Qt equivalent). If you get WM_LBUTTONDBLCLK
(or Qt equivalent) before the timer expires, cancel the timer and execute your double-click action. Otherwise, when the timer expires, execute your single-click event.
On Windows, you can get the double-click time using GetDoubleClickTime()
.
That's about the best you can do - you can't prevent the single click message being generated in the first place on either platform.
Start a timer when you get WM_LBUTTONDOWN
(or Qt equivalent). If you get WM_LBUTTONDBLCLK
(or Qt equivalent) before the timer expires, cancel the timer and execute your double-click action. Otherwise, when the timer expires, execute your single-click event.
On Windows, you can get the double-click time using GetDoubleClickTime()
.
That's about the best you can do - you can't prevent the single click message being generated in the first place on either platform.
edited Nov 22 '18 at 18:28
answered Nov 21 '18 at 14:32
Paul Sanders
5,0451521
5,0451521
WM_LBUTTONDOWN
,WM_LBUTTONDBLCLK
? I would preferQt::MouseButton
constants for this. ;-)
– Scheff
Nov 21 '18 at 15:22
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
add a comment |
WM_LBUTTONDOWN
,WM_LBUTTONDBLCLK
? I would preferQt::MouseButton
constants for this. ;-)
– Scheff
Nov 21 '18 at 15:22
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
WM_LBUTTONDOWN
, WM_LBUTTONDBLCLK
? I would prefer Qt::MouseButton
constants for this. ;-)– Scheff
Nov 21 '18 at 15:22
WM_LBUTTONDOWN
, WM_LBUTTONDBLCLK
? I would prefer Qt::MouseButton
constants for this. ;-)– Scheff
Nov 21 '18 at 15:22
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
@Scheff Sure, if that is easier, I don't know Qt
– Paul Sanders
Nov 21 '18 at 18:59
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
Can you clarify explicitly that single-click up/down events cannot be suppressed in your answer, as you imply and the comment on my question states? Just to make it more complete so I can accept it?
– Mr. Boy
Nov 22 '18 at 13:57
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
@Mr.Boy Done...
– Paul Sanders
Nov 22 '18 at 18:29
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413864%2fis-it-possible-to-suppress-single-click-events-during-a-double-click%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The behavior cannot be changed. The common approach to deal with this is a user interface design, where the single-click operation doesn't interfere with the double-click operation. E.g. in Explorer, a single-click selects an item, whereas a double-click invokes the default operation on the selected item.
– IInspectable
Nov 21 '18 at 15:50