I just did some more basic tests. If you would compile me a version based on this test code version, and just for testing purposes, put a pause in the updating while the mouse is being presses. (please, please, please... and I'll test 2 night)
(But get your sleep etc... I'd rather wait than you get burned out!)
hehe
My thought is, if you do this, I will not have many more lockup problems while zooming.
What is actually making it freeze though? Just because the cpu hits 100% for 2 seconds is no reason to just up and quit, is it?
Hey wait.... maybe the client, or the server needs to decide to throw a way a few packets if it gets over a threshold... Still just poking in the dark here...
There again, are we looking in the right direction? is it maybe the screen trying to redraw or rearange in the middle of something else going on that freezes it. But that something else only happens when connected, because when offline and I load a map I can zoom, and move the map all over, use all the menus, and columns etc, so it is something that only happens while connected.
I will tell you that offline, with a map loaded, *holding* down the zoom button all the way to 10000, and immediately back down to 100, Iand cpu at 100% can do this repetedly without problem. With the same map loaded and connected, the most I have ever gotten to was 250 zoom, and the cpu never even got to 100%.
I even go, then stop, then zoom to 10000 fine.
For what it's worth,
Mr. Doh
As a side note, tell me what you code the client in? I know it's C#, but do you use an interface, do they call it an IDE? (hehe told ya I'm no programmer!) If I get a little more information and get quazi-structured look at the client code, I might could be doing tonights testing and recompiling without wasting your valuable time. Really, thanks again for all this hard work!