Will's the man to figure this out if anybody can.
I appreciate the flattery, but I'm not actually getting very far...
I've just had a little bit of an investigate here, using a debug build of the DLL (because I naturally suspected that!).
Things I have found out:
It's not related to the *launching* process - the freeze will happen at any time that there's typing activity in the text window, but as far as I can tell *only* after you've launched at least one page from DQSD.
It's not connected with the keyboard hook at all (i.e. stopping the hook install altogether doesn't make any difference).
If you attached a native debugger to explorer when it's hung, you learn nothing useful. (There are *heaps* of threads in Explorer, none of which are running through the DQSD dll at the time of the freeze.)
I haven't experimented with the suggestion that 3.0 works - that would be very useful if it's true, as I don't think there's a huge difference in the code which handles every keystroke between the two.
Can someone else verify this?
Cheers,
Will
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ To unsubscribe visit: https://lists.sourceforge.net/lists/listinfo/dqsd-users [EMAIL PROTECTED] http://sourceforge.net/mailarchive/forum.php?forum_id=8601
