New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle winEvents in-process #485
Comments
Comment 1 by aleksey_s on 2009-11-29 08:47 |
Comment 3 by mdcurran on 2009-12-02 01:19 Also, I have some worries about 64-bit compatibility. Certainly your code will compile under 64-bit, but the winEvent_t struct is going to be a different size, due to HWND on 64-bit being double in size. (HWND is a typedef of HANDLE which is a typedef of void*, which is 64 bits, 8 bytes on 64-bit). |
Comment 4 by aleksey_s on 2009-12-03 20:33 Re 64 bit issue: This is my bad. I tried to make all 64-bit compatible but missed this one. |
Comment 5 by mdcurran (in reply to comment 4) on 2009-12-03 23:36
I guess this would be fine. |
Comment 6 by aleksey_s (in reply to comment 4) on 2010-04-09 12:12
Here is quote from msdn (http://msdn.microsoft.com/en-us/library/aa384203%28VS.85%29.aspx):
So I'll do the truncation in 64 bit code. |
Comment 7 by aleksey_s on 2010-12-06 20:19 |
Comment 8 by jteh on 2014-05-29 00:13 |
Reported by aleksey_s on 2009-11-29 08:45
Currently, NVDA sets out-of-process hooks to handle winEvents. though in most cases only few of them are actually used by NVDA, when application spams system with winEvents This makes NVDA lag because of unnecessary marshaling, context switchs and running of python code. Therefore in-process handling will improve performance in cases, when those bombings occur: when huge application starts/finishes, on page loads, in mozilla address bar and so on.
The text was updated successfully, but these errors were encountered: