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
NVDA takes the active profile as the default profile when Plugins are reloaded. #5380
Comments
Comment 1 by jteh on 2015-09-21 21:31 I'm leaning towards dropping this Reload plugins functionality. It was only introduced for developers anyway, but if it's going to continue to cause problems, I'd rather it not be there at all. |
Comment 2 by briang1 on 2015-09-22 11:26 I've never used reload plug ins indeed restart with plug ins dsabled is of more use at times. |
Comment 3 by Javichi on 2015-09-22 22:59 |
I've taken a stab at fixing this in 0460156. It almost works, but there's one remaining problem I haven't found a solution for yet. CC @LeonarddeR. |
Wouldn't it be possible to regenerate all nvda objects from scratch?
|
No. There's no registry of instantiated NVDAObjects. Furthermore, we
have no idea what might be holding a reference to one of the (now
broken) NVDAObjects.
|
Reported by Javichi on 2015-09-21 10:12
I have a profile with a trigger. When it is active and I reload appModules and globalPlugins (with NVDA + Control + F3), profile seems to remain locked. While the application that triggered the profile is running, the profile list indicates that this is triggered, although the application is not in focus. When I close the application, in the profiles list no longer it appears as triggered, but the settings are still active. It seems as if NVDA thinks the profile was the default setting.
Perhaps this error is related to ticket # 3622
The text was updated successfully, but these errors were encountered: