Problem with overlap skins when changing variant

[XANCI]

Assume:
Skin A & skin B, skin B has a series number of variant B1,B2,...;
The positions of A & B make them overlap in some areas;
A & B are in the same level (same "AlwaysOnTop" value) but A is on top of B (A's "LoadOrder" is greater).

1.Change to a variant of B using Manager (just load that variant) , everything goes fine.
2.Change to a variant of B using context-menu (Variants - certain variant) , B goes on top of A instead.

[XANCI]

sometimes B get on bottom of all other skins in same level (with same "AlwaysOnTop" value but with smaller "LoadOrder")

[bobgrosh]

I noticed the same thing.
The load order only keeps skins one on top of the other when you load all of them at once via a theme. Unloading one manually and reloading it, or changing a variant causes the last loaded ini to be on top. It doesn't seem that the load order actually forces the layering of skins displayed on the screen, it just sets the order they are loaded.

[smurfier]

Load order only affects the order that skins are loaded in when Rainmeter is started.

[XANCI]

Load order only affects the order that skins are loaded in when Rainmeter is started.

Is there any ways to keep the order when changing variant?

[Virginityrocks]

I also encountered this problem. Solution please!

[jsmorley]

It doesn't seem that the load order actually forces the layering of skins displayed on the screen, it just sets the order they are loaded.

Thus the name "LoadOrder"...

[dragonmage]

I doubt that it will be possible in any efficient way. My guess is that each Z level, Desktop, Bottom, Normal, etc is a single layer and LoadOrder lays things on that layer in the order you want by painting them in the correct order. I would think that in order for a reloaded skin or variant to appear correctly every skin above it in LoadOrder and Z-Order would have to be reloaded.

[MerlinTheRed]

Doesn't Rainmeter have a central part where all the drawing is handled? You'd just have to keep a list with all the skins in the right order and draw them one after the other then. I imagine such a method must already exist to ensure a skin that is updated more frequently isn't always painted on top of another one that is supposed to be above it and is updated less frequently. Or is it handled by the library you use for drawing and you can't influence it easily?