Comment 1 by briang1 on 2012-02-21 17:55
So how does one only impliment a global plug in on non secure screens? I thought this had to be an all or nothing thing due to the way the plug ins operate.

Comment 2 by mwhapples (in reply to comment 1) on 2012-02-21 19:28
Replying to briang1:

So how does one only impliment a global plug in on non secure screens? I thought this had to be an all or nothing thing due to the way the plug ins operate.

A global plugin can be installed on a per user basis by copying the plugin into the globalPlugins directory of the user's NVDA settings directory (eg. for me in this user account on this system the NVDA user settings directory is C:\users\michael\appdata\roaming\nvda ). The user settings directory can be accessed from the shortcut in the NVDA submenu in the programs list in the start menu. For the system user (for secure screens) there is a separate settings directory in the NVDA directory.

NOTE: I am talking about NVDA from the installer package, portable versions I think may be irrelevant.

@jcsteh @feerrenrut Could you please talk about the feasibility or possibility of this proposal? If it can be implemented taking security concerns and implementation considerations into account, please add the feature label.

I think #6305 is a better solution to this problem. Closing as a duplicate.