What is the reason for initializing configuration as part of install tasks?

[lukaszgo1]

Hi @LeonarddeR At work I will likely need to script installation of rdAccess. While this would be trivial for the most part (just unpacking the add-on to the right directory), in that case install tasks would not execute. Looking at the onInstall function it calls configuration.initializeConfig which adds configuration section to NVDA's config. However this call appears to be unnecessary, since whenever the plugin is initialized, configuration is also initialized

rdAccess/addon/globalPlugins/rdAccess/__init__.py

Line 127 in 88ac948

configuration.initializeConfig()

I cannot imagine a situation in which install tasks would execute, yet plugin initialization would be skipped, however I'm out of touch with NVDA related development for a pretty long time, so it is very likely there is a scenario I haven't considered. From the git log, the code was added in 9c51e36, however this commit just moves code around ,so isn't really helpful in understanding why the call was necessary.

[LeonarddeR]

Hi @lukaszgo1

The reason why I probably added this is that the global plugin isn't the first plugin that is initialized. On the server side of things, the braille display driver and synth driver are initialized before the global plugin. The braille display driver registers a function that allows automatic detection of remote braille, and that detection function accesses the config. However, when it does so, the configuration is initialized anyway. So I think it is safe to remove this install task.

[lukaszgo1]

That makes sense. Thanks! I'm closing the discussion.