So are you saying that I can't have any more than two VU Meter (DirectX 12) entries? (As shows below)

So are you saying that I can't have any more than two VU Meter (DirectX 12) entries? (As shows below)

I'm using 6 locations in my skin where VU Meters can be displayed (simultaneously). All can be different skins or the same.
So I guess this is relevant for me too.

You'll see all 6 but, as above, you'll see only 2 different configurations at any given time.

By configuration I mean a unique combination of layout, mode, levels and the selected skin.

One small clarification for my understanding ... if I have 2 VU meters using the "same skin", will they count as 1 config or 2 configs?
If they are counted as 1 config, then if I change the skin of either one of the VU meter, then it becomes 2 configs?

oops, what are the chances of making more than 2 configurations in the future?

On a different note, Darkone theme has this command for changing the colors of the old vu meter...
Is there a substitute for "Analog VU Meter skins", with the new vu meter?

oops, what are the chances of making more than 2 configurations in the future?

Chances are good. I already made the extension. You'll get as many unique configurations/instances as your computer memory will let you

On a different note, Darkone theme has this command for changing the colors of the old vu meter...
Is there a substitute for "Analog VU Meter skins", with the new vu meter?

If I look at the resources for the original, it is using "IVUMeterWindow" Automation interface to create the menu. This is not something I have implemented.

Now at the risk of being greedy, this would be nice too. Because this is the only thing that is keeping the Darkone theme from going 64 bit.
Unless I can write a script that will change the vu meter colors without the fb.RunMainMenuCommand method.

Quote from: Majestyk on 2024-12-01 04:31:23

Now at the risk of being greedy, this would be nice too. Because this is the only thing that is keeping the Darkone theme from going 64 bit.
Unless I can write a script that will change the vu meter colors without the fb.RunMainMenuCommand method.

I do not know how to do it. All of my attempts have stalled and there is no straightforward documentation for this use case or example. When I load the panel through ActiveX, the object is empty and none of the functions dispatch. It loads successfully and I've checked so many ways to ensure the TLB file is in the right section and ID in the resources. Of all the other component DLLs I've dumped no one seems to export DllGetClassObject() or similar functions. I don't know if they're working with the registry or there is some back channel that I'm not aware of. So, it is a mystery at this point how it is supposed to work, and I'd rather put my energy into something with clearer line-of-sight. Sorry for venting.

If you write a script and you're targeting the original component, using RunMainMenuCommand() seems odd. The component has a LoadSkin() and similar functions to list out what it has that you could just call directly to do what you want.

Modifying the main menu and executing menu commands does not involve ActiveX scripting. What the original component seems to be doing is grouping the "skins" by directory (no nesting appears to be supported). The default panel included in the resources and anything placed alongside the DLL are in the "<Default>" group. The rest are just placed in a different "group" based on the folder name. The context menu is similarly affected, adding a new group popup that selects the directory/group to appear in the list directly below. I need to investigate in the SDK where those functions are.