Help: Switching wallpapers with a button

[Mino_el_Nukenin]

Well, I just made the adjustments needed.
The connector container PNG:
ContainerC2.png
The code adjustments:
- RepeatC=231
- OffsetC=-206
- Y=0 in [MeterContainerC]
That's all, folks.

Thanks, I'll add it !

[Yincognito]

Thanks, I'll add it !

The container image can be perfected at the "edge" between transparency and opacity, as the angular separation is not perfectly straight, but then that's a minor detail anyway (not for us perfectionists though).

[Mino_el_Nukenin]

The container image can be perfected at the "edge" between transparency and opacity, as the angular separation is not perfectly straight, but then that's a minor detail anyway (not for us perfectionists though).

LOL yes, but with such small pixels .png it's pretty hard to see.

I'm tryign to understand how you did it, since I might create some others skin with the same idea of a double sliding.
Basically, you make sure both containers have a relative origin in common, right ?

[Yincognito]

See the result for yourself.

I have to say, it looks great! Well done.

[Yincognito]

LOL yes, but with such small pixels .png it's pretty hard to see.

Good point.

I'm tryign to understand how you did it, since I might create some others skin with the same idea of a double sliding. Basically, you make sure both containers have a relative origin in common, right ?

Quite the opposite. I made sure they're independent and absolutely positioned. It's just a coincidence that they're placed close to one another - that's more a matter of how your skin looks rather than having a functional purpose. Bottom line, the containers needed to be independent of each other in terms of nesting. I chose to position them in an absolute way (i.e. 25 instead of 25r and such) because it was simpler and couldn't go wrong (if some other meter would have been placed in front of them, for example).

That being said, that has nothing to do with how I did the "double sliding" (i.e. one slide immediately after the other). It's all about putting everything in one slider / ActionTimer measure, separated of course by wait times. As far as ActionTimer is concerned, these two slides are a single movement, because they both belong to the same ActionListN option (i.e. ActionList1 for the slide out, ActionList2 for the slide in).

Frankly, this one slide immediately after the other couldn't have been done another way, since there is no way of knowing when the ActionTimer measure finished the animation, other than placing something (another animation, in this case, i.e. the connector one) right after the first (i.e. the panel one).

[Mino_el_Nukenin]

Good point.


Quite the opposite. I made sure they're independent and absolutely positioned. It's just a coincidence that they're placed close to one another - that's more a matter of how your skin looks rather than having a functional purpose. Bottom line, the containers needed to be independent of each other in terms of nesting. I chose to position them in an absolute way (i.e. 25 instead of 25r and such) because it was simpler and couldn't go wrong (if some other meter would have been placed in front of them, for example).

That being said, that has nothing to do with how I did the "double sliding" (i.e. one slide immediately after the other). It's all about putting everything in one slider / ActionTimer measure, separated of course by wait times. As far as ActionTimer is concerned, these two slides are a single movement, because they both belong to the same ActionListN option (i.e. ActionList1 for the slide out, ActionList2 for the slide in).

Frankly, this one slide immediately after the other couldn't have been done another way, since there is no way of knowing when the ActionTimer measure finished the animation, other than placing something (another animation, in this case, i.e. the connector one) right after the first (i.e. the panel one).

Oh okay, I get it. I'll try to do the same for others skins then to see if I understood well.

[Mino_el_Nukenin]

Okay so i'm onto anotehr skin.
Which is (for now) mainly a visual one.
It is/will be composed of [MeterShapes]. But I'm not managing to have correct shape, in terms of size.
Then i'll want some of these shapes to be in a movement.

Visually this part of the skin is a black circle (ellipse) with a 89 radius + a stroke of 1px, so a 90 radius ellipse in total.
And what I'm trying to add are different arc above the black circle.
See the image joined : My idea is to recreate the arcs like the different blue and green arcs in the image.
I already have another skin like the circle with an eagle in the middle, which will be above and have no interaction with the one i'm creating.

This what I have so far :

Code: Select all

[MeterShapes]
Meter=Shape
Shape=Ellipse 90,90,89 | Fill Color 0,0,0 | StrokeWidth 2 | Stroke Color 255,255,255
Shape2=Arc 14,90,90,14,75,75,360,0,0,0 | StrokeWidth 15 | Stroke Color 255,255,255
AntiAlias=1

I can't manage to have the right fitting for the arc, I want it to be perfectly against the stroke then i'll adapt the depth of it.

[balala]

See the image joined : My idea is to recreate the arcs like the different blue and green ars in the image.

To convert an image to Shape meter i recommend to use theAzack9's Vector Converter. Unfortunately it'll convert only .svg files to Shape meter, but there are possibilities to convert the .png (or .jpg or whatever supported image format) image to .svg, then apply the tool to create the appropriate Shape meter. Not too easy, but not impossible either.
jsmorley shortly explained here what you have to do for such a conversion. If interested, give it a try.

[Mino_el_Nukenin]

To convert an image to Shape meter i recommend to use theAzack9's Vector Converter. Unfortunately it'll convert only .svg files to Shape meter, but there are possibilities to convert the .png (or .jpg or whatever supported image format) image to .svg, then apply the tool to create the appropriate Shape meter. Not too easy, but not impossible either.
jsmorley shortly explained here what you have to do for such a conversion. If interested, give it a try.

I don't want to convert an image into a shape. I want to create shapes (arcs) based on the ones on my image, as a pattern.
Btw, I don't see the point in converting an image into shape, just use an image, that's easier; or create a shape.

EDIT : Nevermind the shapes and my actual code, I'll design the shapes I need on Photoshop, that's easier.

[balala]

Btw, I don't see the point in converting an image into shape, just use an image, that's easier; or create a shape.

Depends on what you want to use it for. A Shape meter can easily be modified by Rainmeter code, while an image can't be. On the other hand a shape meter which represents an image can be extremely large, as you saw on the posted link, jsmorley's avatar image created as Shape meter requires 10,000 lines. Way too much.