[Nvda-dev] [NVDA] #544: A possibility to reload appModules without NVDA restart

NVDA Trac trac at nvda-project.org
Sat Feb 6 23:08:25 UTC 2010


#544: A possibility to reload appModules without NVDA restart
-------------------------+--------------------------------------------------
 Reporter:  aleksey_s    |       Owner:  aleksey_s
     Type:  enhancement  |      Status:  assigned 
 Priority:  minor        |   Milestone:           
Component:  Core         |     Version:  trunk    
 Keywords:               |          Os:           
Blockedby:               |    Blocking:           
-------------------------+--------------------------------------------------

Comment(by jteh):

 NVDAObject instancdes have a weakref to their appModule, not a strong
 reference, so this isn't an issue.

 There are other issues, though. An app module (and in future, a global
 plugin) isn't restricted in terms of what it can do within NVDA. That is,
 there is no separate scripting environment like there is with a lot of
 other ATs. This gives us a lot of power and flexibility, but it also means
 that reloading could be dangerous or, at the very least, very tricky. For
 example, an appModule might add something to some internal structure, but
 when it is reloaded, it will then add it again. You might be able to get
 around this by having a function which gets called just before the module
 unloads.

 I wonder, though: would a keystroke to restart NVDA suit your purposes? At
 present, you have to press a few keystrokes, but I've often thought having
 a restart keystroke within NVDA. It's not quite as fast, but it's not
 particularly slow either.

-- 
Ticket URL: <http://www.nvda-project.org/ticket/544#comment:3>
NVDA <http://www.nvda-project.org/>
A free and open-source screen reader for Windows


More information about the Nvda-dev mailing list