Will
January 2, 2009, 5:56am
1
Hello, I have submitted a patch for SDL in bug 661 but as I posted on Bugzilla I
think there is something wrong with my build environment. Is there any way that
someone could apply this patch and do a compile for MinGW with
–disable-stdio-redirect for me?
Thanks a lot!
–Bill
Will
January 3, 2009, 1:47am
2
Never mind my last post (not a build environment problem).
Sam - did the mouse event code on windows begin to undergo a rewrite recently?
If so I’m assuming it?s to support multiple mice?
It looks like SDL is no longer reporting which window a mouse event comes from.
Also relative mouse moments no longer work.
This drove me nuts because I assumed that the mouse event code was already
finished
Thanks
–Bill
Never mind my last post (not a build environment problem).
Sam - did the mouse event code on windows begin to undergo a rewrite recently?
If so I’m assuming it???s to support multiple mice?
Yes, it did.
It looks like SDL is no longer reporting which window a mouse event comes from.
Also relative mouse moments no longer work.
Can you report the bug in bugzilla? (http://bugzilla.libsdl.org )
Thanks!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
Will
January 3, 2009, 3:39am
4
Done! (Bug 663)
lol this bug got me confused when I reported/patched bug 661.
Your welcome / thanks!
–Bill
Done! (Bug 663)
Thanks! This should be fixed in subversion now.
lol this bug got me confused when I reported/patched bug 661.
Can you re-enter bug 661 after testing with bug 663 fixed? Your current
report is pretty confusing.
Thanks!
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
Will
January 3, 2009, 8:51pm
6
Thanks! This should be fixed in subversion now.
Downloaded from SVN and the mouse code works great!
Turns out I also forgot to copy over the new SDL headers into my project lol.
Can you re-enter bug 661 after testing with bug 663 fixed?
Sure, I created a new patch for svn and its now… Gulp! bug #666
Your current report is pretty confusing.
lol
The new report should make more sense
P.S. That was fast! BTW I also found a full screen issue (bug #660 )
Thanks!
–Bill