We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2928 - Delayed click event Windows Forms in same XY location
Summary: Delayed click event Windows Forms in same XY location
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: events (show other bugs)
Version: 2.0.3
Hardware: x86_64 Windows 8
: P2 minor
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-29 13:52 UTC by danellos
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description danellos 2015-03-29 13:52:19 UTC 
When 'hooking' SDL2 into a foreign window created by System.Windows.Forms.Form in C# (via an interop library), there is a notable delay of roughly 800ms between successive mouse down/up events being fired when the user attempts to click in the same X/Y location repeatedly (AKA spam-clicking). The delay does not happen when the user "spam clicks" anywhere in the window, but in different X/Y locations.

I marked this as a minor bug, because as a workaround, I decided to use the built-in Windows Forms click event handler instead. It should be noted that System.Windows.Forms.Form is a standard win32 window created in .NET.

This does not happen when using any window created by SDL2.

For context on what I am doing, I am using SharpDX in tandem with SDL2# to create a framework for some games I intend to create.
Comment 1 Sam Lantinga 2017-08-13 03:29:05 UTC 
Any way I can get a test case so I can reproduce this here?
Comment 2 Ryan C. Gordon 2018-08-06 21:20:21 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.