Store plugin configurations along with profile / profile specific

[Ruediger]

Hello,

I ran in following problem, that the plugin configurations are globally. Usually I run 2 to 3 NINA instances parallelly. When using plugins like “Hocus Focus” the parameters a device dependent and differ from gear to gear. e.g. Focal Length, noise, etc. Currently you have to start each instance and re-enter all the config parameter which differ.

This could be als interesting when you configure Ground Station / Pushover individually for each instance with its own key. Also others.

Solution proposal: Either store it along with profile or have plugin profiles which are linked to dedicated NINA profiles, which would be most versatile.

Thx!
Rüdiger

‌

[Stefan B]

Plugins can already store profile specific values. It is up to the plugin author to decide if plugin specific settings are app wide or profile wide.

[Ruediger]

Hi Stefan, thanks for the quick reply. I have created a GitHub issue for that.

Rüdiger

‌

[George Hilios]

Ruediger, I am using this very mechanism already with Hocus Focus. Please let me know if there are issues with it. All HF settings are saved as part of your profile

[Ruediger]

Hello George,

Many thanks for stepping in. Yes, there is an issue. I have attached the description.

1. I have profile for the CDK with “long focal range” (left, 2563mm), right the TEC with “Typical” (980mm) (upper screen shot)
2. I close CDK, I close TEC
3. I load CDK and TEC again, and the CDK Profile has the value of the TEC. (lower screenshot)

It looks like the last saved profile is overwriting all values.

Many thanks for having a look into.
Rüdiger

‌

[Ruediger]

Fixed in 21

[Stefan B]

Removing version: 2.0 Beta (automated comment)