lysy1993lbn wrote:It's just awesome! I totally love it
But.. what about groups? I'd like to make my dock slide on hover, do I have to apply 14 bangs to do it?
From the original post:
Kaelri wrote:Variables
All of the bangs above have an optional variable name parameter. If supplied, the transition changes this variable's value, instead of meter options. (You must still provide the name of at least one meter to be updated during the transition.) The variable name 'Auto' will use the default ("automatic") behavior.
You may also use meter groups if you target a variable. You can mix meters and groups however you want. This can be useful if you want one transition to affect a large number of meters, or if the automatic behavior is not what you want.
lysy1993lbn wrote:Or is possible to move whole skin from another one?
Now I have separate skin to show with fade effect my dock which basically trigger MouseOverAction=[!ShowFade "woodock"][!Hide "woodock\$widgets\position"] at hover on it.
You could easily modify the script to move skins instead of meters. However, you would need a way to get the starting location of the other skin. You can see this thread for some ideas on how to do that.
ScoobSTi wrote:This is the most beautiful skin I've ever seen!
I'd like to integrate part of this into my Android skin, if you don't mind (with credit of course!).
Feel free. :) Be aware, though, that it won't work properly on systems with multiple monitors. (The text will stick out into the monitor on the right.)
Here I have to agree with the previous caller skin is great pity that for the time being, you can type one address RSS
Every day I look here or here Kaelri not added a promised a version for more addresses and impatience I bite nails!
wiedzmawiedzma wrote:Here I have to agree with the previous caller skin is great pity that for the time being, you can type one address RSS
Every day I look here or here Kaelri not added a promised a version for more addresses and impatience I bite nails!
Lua's "GetOption" doesn't recognize options inherited from MeterStyles right now. So you need to set FontColor individually on both Line1 and Line2. (This is something that annoys the hell out of me, too; we're hoping to fix it in the semi-near future.)
Setting FontColor=255,255,255 or FontColor=ffffff on both [Line1] and [Line2] gets rid of the error but I still don't see [Line2] after clicking on [Line1].
Mordasius wrote:Setting FontColor=255,255,255 or FontColor=ffffff on both [Line1] and [Line2] gets rid of the error but I still don't see [Line2] after clicking on [Line1].
Sorry, I had only checked the skin for the cause of the "Xi" error, not other problems. The "Fade" commands in this script only affect the meter's transparency; they do not change the Hidden state. So Line2 remains hidden even while it's "fading in." If I understand what you're trying to accomplish, this should work: