Skip to content


Unify and refactor NVDA in-process code #385

nvaccessAuto opened this Issue · 4 comments

2 participants


Reported by jteh on 2009-08-08 03:50
All of NVDA's in-process code should be unified into NVDAHelper. This will reduce duplicated code and greatly ease the process of adding new in-process code. NVDAHelper will handle the setting of system hooks and components will then register hook callbacks with NVDAHelper to be executed when the hook is fired. nvVBufLib will be merged into NVDAHelper, which means it will no longer be a separate library. This is becoming far too difficult to maintain and the advantages greatly outweigh the disadvantages.

Most of this work is already complete. However, we should be tracking these issues properly. :)
Blocking #246, #309, #375, #381, #386, #387


Comment 1 by jteh on 2009-08-08 03:52
Bzr branch:
This also fixes some crashes in nvVBufLib due to better detection of when a buffer should be terminated.


Comment by aleksey_s on 2009-08-10 16:12
(In #387) Fixed in bzr nvdaHelperRewrite r2932.
Btw, I am thinking about organizing our node-specific code somehow. May be separate code for each node into functions and put them into array or map...


Comment 8 by jteh on 2009-08-17 10:58
Merged in r3110.
State: closed

@nvaccessAuto nvaccessAuto added this to the 2009.1 milestone
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.