WM_NCHITTEST / WM_SETCURSOR

[slotdev]

Hi

My app has 2 windows on 2 separate monitors. When I click a button on one screen, I have to click twice to get the button to function, and again twice on the other screen, etc. So it seems that the window (cursor?) doesn't have focus and my app is getting the mouse XY for the wrong screen, as I can click one part of a screen, and it actions the button on the other screen (in the same XY position).

I have another app, on an older version of SFML (2.0) which works fine.

I have produced log files of WM_ messages, and the difference is, on the app that works OK, I am seeing this very often (every frame, I think):

WM_NCHITTEST
WM_SETCURSOR

I see the MouseMoved code is very different from 2.0 to 2.1.....but I don't think this would be the problem.

Does anyone have any ideas?

Ed

[Laurent]

This is a known bug that has been fixed, you should try the latest development version.

[slotdev]

Thanks Laurent, I'll check it out now.

Any ideas why it worked OK on 2.0, but not on an older 2.1?

[zsbzsb]

When SFML 2.1 was released it included a "bug fix" for some win32 implementation stuff, however the fix actually caused more issues (like the one you described) and no one caught the bug before 2.1 was released.