I have a mapbasic tool that relies on a series of Windows API calls that allows the user to click one point and while sliding the cursor to another point, it displays the current distance and azimuth of the line as you move the cursor around. A second click exits the loop and reports the two end points. It has worked fine since I wrote it a couple of years ago, and still works perfectly in Win98, NT, Win2K and Me. But it behaves a little flaky in MapInfo running under Microsoft's XPee. In XP the status bar is not holding the display (it appears quickly and then vanishes until the mouse moves again, and the 2nd mouse click (even if it occurs within the map window) tends to switch focus to the background application as if if you had pressed Alt-Tab.
It only flakes out under XP and not all the time -- sometimes it works fine. And it always works fine in any other Windows O/S I've tried. So I'm wondering if XP treats any of the following Windows APIs differently: ClientToScreen GetAsyncKeyState GetClientRect GetCursorPos GetDC GetSystemMetrics LineTo LoadCursorA MoveToEx ReleaseDC ScreenToClient SetCursor SetROP2 ShowCursor If anyone notices a red flag here, could you let me know which API(s) I need to check in detail? - Bill Thoen --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 5168
