-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
GDIHooking library for NVDA #40
Comments
Attachment GDIHookHandler.py added by pvagner on 2008-03-26 15:41 |
Attachment gdihook.zip added by aleksey_s on 2008-04-03 15:37 |
Comment 1 by pvagner on 2008-03-16 22:17
Some notes |
Comment 2 by aleksey_s on 2008-03-22 19:22
|
Comment 3 by aleksey_s on 2008-03-25 08:00
Now there precompiled debug versions of both libs, named GDIHook_debug.dll and GDIHookHandler_debug.dll. you can put their in nvda folder and delete suffix "_debug", then libraries will provide a log with all happened stuf and you can see what is incorrect. log can be found at your_temp_dir/gdihook.log |
Comment 4 by aleksey_s on 2008-03-25 20:45
|
Comment 5 by aleksey_s on 2008-03-26 12:32
|
Comment 6 by aleksey_s on 2008-04-02 18:07 |
Comment 7 by aleksey_s on 2008-04-03 15:39 |
Comment 8 by jteh on 2008-05-31 23:50 |
Comment 9 by jteh on 2008-06-23 11:10
Are you using bzr for version control? If so, we should get you an account on our hosting server at some point so you can publicly post the bzr branch. I am moving this out of 0.6. This does not mean that it will not go into 0.6, but it means that it will not block 0.6 if it's not ready when 0.6 is to be released. |
Comment 10 by jteh on 2008-06-24 02:26
|
Comment 11 by aleksey_s (in reply to comment 9) on 2008-07-30 08:47
yes, i have worked around some major mechanizms of intercepting and attaching/unattaching, as well as storing data. i decided to store each hooked data in the in-process structures, and write it in shared memory when needed. so now each gdihook library when injecting creates some hided window to receive commands, and uses shared memory as some type of stack to receiving and sending data to handler. however, all problems i noted earlier still exist (e.g. with clearing unnecessary data, controls in dialogs etc).
look at my earlier comments.
yes, i am.
i am completely agree. |
Comment by jteh on 2008-08-03 06:35 Note that the "Open With" menu in Vista does not seem to suffer from this issue. |
Comment 13 by Bernd on 2008-10-28 19:13 |
Comment 14 by aleksey_s (in reply to comment 13) on 2008-10-28 19:56 |
Comment 15 by aleksey_s on 2008-12-28 10:18
for me, even major is your opinions on the first question (about architecture), if you are unfamiliar with all this lowlevel technical details i will try to investigate they myself. |
Comment 16 by Bernd on 2010-01-08 12:24 is there any further progress on this? I ask because some german people asked me. |
Comment 18 by mdcurran on 2010-03-07 11:13 This implementation is in c++, and is built right in to nvdaHelper. I'd probably suggest that for future work on the new implementation we create new tickets. Some notes:
As I have been develping this on Windows 7, I know it sort of runs ok here. Havn't really tried on XP/Vista yet, though if there are issues, its most likely in my bad coding of critical sections etc. |
Comment 19 by mdcurran on 2010-03-07 12:30 As for Vista, I just tried this branch on my wife's computer, and all works fine there. I'm interested if any other developer is able to run this branch on XP sp2/3, with out it freezing on startup? I'll look more in to this in the coming days. |
Comment 20 by pvagner on 2010-03-07 19:43 str
Actual resultsAs long as the open dialog comes up NVDA crashes. Nothing usefull is written to the log, I can't kill it using the task manager nor using other memorized methods such as dismissing the dialog to close it. I can't start another copy of NVDA at this point and the only way I can use to recover from this crash is to reboot. expected resultHeh I think I shouldn't expect anything at this stage. Good job mick anyway. Perhaps I am at least a bit helpfull. |
Comment 21 by jteh on 2010-03-07 22:36 |
Comment 22 by mdcurran on 2010-03-08 04:45 |
Comment 23 by pvagner on 2010-03-08 18:50 |
Comment by jteh on 2010-03-23 10:53 This issue requires display hooks to fix. |
Comment by pvagner on 2010-03-25 08:00 |
Comment 26 by jteh on 2010-05-13 04:02 |
Comment 27 by jteh on 2010-05-13 04:02 |
Comment 28 by jteh on 2010-05-13 04:07 |
* Typo on paragraph nvaccess#101 * Plus minor fixes (proposals)
Reported by aleksey_s on 2008-03-16 21:31
i am implementing a library, with which nvda can to have access to the text, which is written by GDI functions directly. this is the delphi sources, as well as precompiled binaries. GDIHook.dll is an in-process dll which making hooks to api, GDIHookHandler.dll is manager for it. GDIHookTest.exe is an test application which works with GDIHookHandler exported functions.
note, that all stuff can have bugs and might crash your system!
Blocking #151, #200, #582, #605
The text was updated successfully, but these errors were encountered: