Still searching for an answer here, but it looks more and more like XP is the problem. Upgrading XP with their inevitable Service Pack (SP1 in this case) seems to cure some of the problems and lessen the frequency of the rest. Upgrading to SP1 might help your mouse problem too. Throwing XP out into the trash and going back to Win2000 might be even a better idea.
- Bill Peter Horsboll Moller wrote: > > I haven't any actual experience in using these functions under XP, but we > have discovered another strange behavior in MapInfo under XP. > > We are using Logitech mice and also the logitech Mouse driver in a version > 9.75. > > The problem we are discovering is that the mouse acceleration is very slow > when the louse is moved inside MapInfo. If you move the mouse on the desktop > or in another program you might only need to move your mouse a few cm to > move the cursor from the one side of the screen to the other. But when you > are working in MapInfo you'll have to move the mouse 2-4 times that > distance, so you get really tired using the mouse inside MapInfo. > > Has anyone had similar experiences and a solution for this ? > > TIA, > Peter Horsboll Moller > COWI A/S > > -----Original Message----- > From: Bill Thoen > To: MapInfo-L > Sent: 27-01-03 23:49 > Subject: MI-L Windows APIs in MB app screwing up under XP > > 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: 5180
