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 729 - SDLCreateWindowFrom does not register for mouse input
Summary: SDLCreateWindowFrom does not register for mouse input
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.1
Hardware: x86 Linux
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-23 23:33 UTC by Daniel
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:

Attachments
Patch to fix the issue (626 bytes, patch)
2009-04-23 23:33 UTC, Daniel 		Details | Diff
View All 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 Daniel 2009-04-23 23:33:08 UTC 
Created attachment 321 [details]
Patch to fix the issue

SVN r4460 forgets to register win32 mouse input
the patch adds the registration at the end of CreateWindowFrom
Comment 1 Sam Lantinga 2009-09-26 03:01:18 UTC 
I'm not sure whether SDL should be handling events on windows that it didn't create... ?
Comment 2 Sam Lantinga 2009-12-14 22:52:02 UTC 
I'll be adding an API to specify whether you want input on a foreign window.
Comment 3 Ryan C. Gordon 2018-08-06 21:20:24 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.