First of all, I'm new to the forum and programming with rainmeter. I'm from Brazil and my English writing is very bad. Sorry...
I'm trying to program a skin and I'm having troubles. I'm based on several posts here in the forum as well as skins that I'm downloading on the internet.
Until now I have been able to make the images fadein on mouseover. however, only works when the mouse comes from outside the skin. when I am inside the skin and I direct the mouse to the next image the effect does not work.
We don't have your images, so it's hard to test, but I'm quite sure that what is happening is that those image meters overlay each other. That will completely confuse the "mouse over / mouse leave" stuff, as the mouse will be detected by both image meters.
I'm planning to make a background that changes the color on mouseover. for now I'm working with slices of 96x108 but if I can make the effect work, I will reduce the size of the slices.
So the issue is that you are using the same "fader", or more to the point the same "variable" for both images, and that is creating a conflict. If you separate them:
jsmorley wrote: ↑December 11th, 2018, 8:23 pm
I'm quite sure that what is happening is that those image meters overlay each other. That will completely confuse the "mouse over / mouse leave" stuff, as the mouse will be detected by both image meters.
I think it's not so simple.
andersonventura wrote: ↑December 11th, 2018, 8:01 pm
Until now I have been able to make the images fadein on mouseover. however, only works when the mouse comes from outside the skin. when I am inside the skin and I direct the mouse to the next image the effect does not work.
The issue is that you're using one single variable (Alpha), which should have to be used to set the transparency of two meters: [Slice_01] and [Slice_02]. I probably would use two different variables (for example Alpha1 and Alpha2), to set the transparency of meters. for this, besides adding the variables, you also have to add further options to the [Fader] ActiontTimer plugin measure, or even better, to duplicate the measure, to can set the values of the variables independently. What you definitely shouldn't have to do is to directly set the value of a variable (in this case the value of Alpha), through some !SetVariable bangs.
jsmorley wrote: ↑December 11th, 2018, 8:57 pm
BTW, there is really no need for the !SetOption bangs on the mouse over / mouse leave actions. it will work smoother without them:
I would just like to add...
With [!redraw] the skin was consuming 26% of processing, and fluidity was very compromised! Removing [!redraw] is running smoothly & faster and consuming only 15% of processing!
There is no need to have the skin trying to update once every millisecond. First, it can't, and second, that will be very CPU expensive.
Put back the [!Redraw]
Remove the
SkinWidth=1920
SkinHeight=1080
There is just no need to have the skin use the entire screen. That is just pointlessly expensive on each redraw. If the intent is to "fix" the position of the skin in a certain spot on the screen, and preclude accidentally moving it, that can be done other, far less expensive ways.
I think where you got the Update=1 from is a misreading of a skin where you saw Update=-1
Update=-1 means "never update automatically again after the very first update", which actually would be good for this skin, since it is entirely "interrupt / event driven" by the mouse.
This line:
U=[!UpdateMeasure Fader][!UpdateMeter *][!Redraw]
Will take care of all the "updating" that is needed, and only as needed.
