[Suggestion] Suppress !DeactivateConfig warnings in the log

[SilverAzide]

Hello,
I have a suggestion for a very minor enhancement to the !DeactivateConfig bang.

Sometimes folks have skins with a parent-child relationship. For example, a configuration skin with a pop-up color picker skin, or a weather skin with a pop-up "location picker" skin. It is possible in these scenarios to close the parent skin and leave the child skin active, which isn't a huge deal, but is just a little messy. The simple fix for this is when closing a parent, to deactivate all child skins to clean everything up.

Unfortunately, deactivating a skin that isn't active leaves an annoying message in the log:
!DeactivateConfig: "MySkin" not active

I'm not sure how helpful that message is, but in any case there's precedent elsewhere for suppressing unwanted log messages (like WebParser). Could a tweak be added to suppress !DeactivateConfig logging for these type of "close skin whether it's open or not" type of use cases?

I know it is possible to use the ConfigActive plug-in and some additional coding to get fancy, but the ROI for all that is pretty low. I guess for completeness, !DeactivateConfigGroup would also need this same tweak. EDIT: !DeactivateConfigGroup does not output a log message, as described below.

Thanks for listening!

[balala]

I guess for completeness, !DeactivateConfigGroup would also need this same tweak.

!DeactivateConfigGroup is perfect, avoiding the error message.
To check, replace the !DeactivateConfig bangs with a [!DeactivateConfigGroup "MyGroup"] (use a non-existing config group name). Additionally it's easier to use such a bang, being much shorter than the numerous !DeactivateConfig bangs.
So just include the "child" configs into a group and use !DeactivateConfigGroup.

[SilverAzide]

!DeactivateConfigGroup is perfect, avoiding the error message.
To check, replace the !DeactivateConfig bangs with a [!DeactivateConfigGroup "MyGroup"] (use a non-existing config group name). Additionally it's easier to use such a bang, being much shorter than the numerous !DeactivateConfig bangs.
So just include the "child" configs into a group and use !DeactivateConfigGroup.

Excellent! Thanks for the tip!

[balala]

Excellent! Thanks for the tip!

Did you try it out? Did it supress the message?

[SilverAzide]

Did you try it out? Did it supress the message?

Yep, works great and it's easier too, as you mentioned.

[balala]

Yep, works great and it's easier too, as you mentioned.

I'm glad.