Hi,
Hi have seen the SDL code.
FILE = src/video/wincommon/SDL_sysevents.c
FUNCTION = WinMessage
The problem is that if we receive a NOT-CLIENT message we call
DefWindowProc (at the end of the WinMessage function).
In this case the DefWindowProc is blocking.
A solution could be manage directly these events.
Moving the window is not too difficult (I think … and hope …)
but we have to manage the small buttons on the right and the button on
the left.
I have tried to call the DefWindowProc (in response to NOT_CLIENT
messages) using a thread (to execute it in background) but it does not
work because (I think) the next calls to DefWindowProc are blocked.
It is not easy solve in a good way this problem.
Thanks for replays.
PaoloOn Tue, Aug 19, 2008 at 7:28 PM, David Olofson wrote:
On Tuesday 19 August 2008, Aki Koskinen wrote:
On Tuesday 19 August 2008, David Olofson wrote:
On Monday 18 August 2008, Paolo Minazzi wrote:
[…]
When I press mouse button on the taskbar of my application, my
application STOPS until I release the mouse button.
[…]
I know absolutely nothing (well, very little) about Windows but
wasn’t the original question about taskbar and not title bar? Or did
I misunderstand something?
[…]
Well, the original poster wrote “the taskbar of my application”. Since
a Windows application doesn’t have a taskbar of it’s own, and since
I’ve run into the “titlebar grab” problem before, I assumed that was
what it was about. 
Not that clicking either one should stop your application from
responding.
Exactly - but it does. (Actually, holding the button down on it,
rather than clicking.)
And to further poke about a subject I don’t really know about:)
Writing duplicate code for work that a window manager should handle
seems like a wrong path in every imaginable situation.
It is definitely wrong, and also ugly and somewhat risky, but as the
bug is there in all Windows versions, including the current ones
(with the possible exception of Vista; haven’t checked), all we can
do is work around it, in cases where it matters.
Of course, we can also ignore the problem, but all that does is have
users blame us for writing crappy applications… Just re-read the
original post to see what I mean: It’s blamed on SDL.
//David Olofson - Programmer, Composer, Open Source Advocate
.------- http://olofson.net - Games, SDL examples -------.
| http://zeespace.net - 2.5D rendering engine |
| http://audiality.org - Music/audio engine |
| http://eel.olofson.net - Real time scripting |
‘-- http://www.reologica.se - Rheology instrumentation --’
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org