Bugs & Feature Suggestions • Multiple Config handling

Hello,

When dealing with multiple active configs and one would want to change something on all of them at the same time we have tools like skin group bangs and using “*”, which are great.

However when it comes to meter\measure bangs there’s only 2 ways of sending the same bang to multiple configs, either by creating a bang per config, or using “*” on the config option.

However, using the latter means that the bang will be sent to all active configs wether they belong to the current skin or not, so if not careful one could set undesired options on undesired skins that have the same section name, or group name.

I noticed it because at first I thought this would only affect configs on the same skin so I was using generic group/section names like “text” in most of my skins. Therefore when sending a config “*” bang I would obviously affect skins that were not planned to be affected in the first place.

What would be nice to have is a way to specify the configs we want to change on a single bang instead of affecting all of them or having to duplicate the same bang multiple times.

So this:
would be instead

[!SetOptionGroup Text FontColor 255,255,255 “config1|config2”]

This way we can specify which configs should be affected without unnecessary bang duplication.

This could even allow to set variables like

Configs=config1|config2

And use

[!SetOptionGroup Text FontColor 255,255,255 “#configs#”]

Thanks for reading yet another one of my ideas.

Statistics: Posted by RicardoTM — Yesterday, 3:31 pm — Replies 0 — Views 32

---