Maybe not the fault of Microsoft?
If you move your mouse continually the query may not fail. Do not stop moving
11–20 of 168 posts
Re: If you move your mouse continually the query may not fail. Do not stop moving
#12Re: If you move your mouse continually the query may not fail. Do not stop moving
#13My friend's dad, a Math/CS teacher, did not believe me until I showed him.
Re: If you move your mouse continually the query may not fail. Do not stop moving
#14>> This problem has been reported when querying an ORACLE 7.3 data source by using the following ODBC drivers. Sqo32_73.dll is manufactured by Oracle Corporation. Microsoft makes no warranty, implied or otherwise, regarding this product's performance or reliability. Maybe not the fault of Microsoft?
I guess if it's an event loop thing one could also alternate 'z' and 'x' as fast as possible :-)
Re: If you move your mouse continually the query may not fail. Do not stop moving
#15Re: If you move your mouse continually the query may not fail. Do not stop moving
#16Re: If you move your mouse continually the query may not fail. Do not stop moving
#17When I was a kid, Windows ME would hang on startup unless I kept moving the mouse. My friend's dad, a Math/CS teacher, did not believe me until I showed him.
The first versions of Windows NT would crash if you moved the mouse while shutting down. Like a child throwing a tantrum because it's bed time...
Re: If you move your mouse continually the query may not fail. Do not stop moving
#18Re: If you move your mouse continually the query may not fail. Do not stop moving
#19Re: If you move your mouse continually the query may not fail. Do not stop moving
#20This reminds me a bit of how networking works on OS X and iOS (at least if you are using the "standard APIs" the way they are supposed to be used: The networking that is going on is tied to a runloop. Some apps tie the networking stuff to the main run loop. You can see which apps do that by simply opening a context menu in the app somewhere or open a regular menu from the app's main menu. The run loops will be "halte…
This isn't really correct. Runloops have modes. Often networking happens in a mode that is not restricted (see NSRunLoopCommonModes here https://developer.apple.com/library/ios/documentation/cocoa/... ). If you are running your network code in default mode on the main thread (problematic doing that and it's probably better to use async methods these days) then yes that can happen but it's usually programmer error. On…
I am aware of what you mention in your answer. In my statement I simplified quite a bit. I know that runloops have different modes. What I was saying is that if you just use the "defaults" then you will see the phenomenon that I described.
And I don't think that it is a programmer error if you use the defaults... but sure: These days you would probably just use a framework or take care of these details...
May I know why you have reimplemented CFRunLoop?