Harold Hunt wrote:
> Was that with your modified server or with the Test57 server? I had to
> reimplement the showing/hiding logic in the Test57 server since I couldn't
> use your patch directly... so I need to know which one has the problem.
It was with my modified version. I'm going to look at
Jehan,
> A static would do the job but, by personnally, I don't like static in a
> function. It's easy to miss the "static" keyword when reading the code
> which then make it hard to understand (or at least, I missed it. Several
> times already I spent a few hours to try to understand why the cod
Jehan,
> However, I already got on a
> couple occasions the pointer visible with no way to hide it.
Was that with your modified server or with the Test57 server? I had to
reimplement the showing/hiding logic in the Test57 server since I couldn't
use your patch directly... so I need to know whic
Harold Hunt wrote:
> As I thought, the documentation for WM_NCMOUSEMOVE does say that you are
> supposed to return 0 if you process that message. However, they fail to
> mention that things such as button highlighting are handled by
> DefWindowProc, which you still need to call if you want to pre
Jehan,
> - Last, WM_NCMOUSEMOVE calls the default winproc. This should fix
> the min/max/close button highlight problem on WinXP (Although I don't
> have XP so I can't test)
That's an excellent catch. I went back and read the Platform SDK docs about
WM_NCMOUSEMOVE:
http://msdn.microsoft.com
