You can't define a [Variable] using one of the built-in #VARIABLE# items Rainy has added.
For instance:
I have a dock that has always used this approach
[VARIABLES] LINKS="C:\Users\Jeffrey Morley\Documents\Rainmeter\Skins\Shadow\WideDock\links\"
[MeterCOMPUTER_BUTTON] Meter=BUTTON X=77r Y=0 ButtonImage=images\button.png ButtonCommand=!Execute ["#LINKS#computer.lnk"]
Works great. With 1.0 I said "Oh cool. I can change this to"
[VARIABLES] LINKS="#CURRENTPATH#links\"
[MeterCOMPUTER_BUTTON] Meter=BUTTON X=77r Y=0 ButtonImage=images\button.png ButtonCommand=!Execute ["#LINKS#computer.lnk"]
While it may seem intuitive to many users, this will not work. You do not seem to be able to define a variable by using a variable as part of the definition.
I can of course directly use the built-in variable in the ButtonCommand and it works great.
[MeterCOMPUTER_BUTTON] Meter=BUTTON X=77r Y=0 ButtonImage=images\button.png ButtonCommand=!Execute ["#CURRENTPATH#Links\computer.lnk"]
Trouble is, I'm almost better off with the old method as I have more flexibility to move the location I put the links in without having to change it in every meter. I think it would add a huge amount of usefulness to the built-in variables if we could use them as part of a [Variable] definition.
Comment #1
Posted on Aug 12, 2009 by Swift CamelThis is now possible in r178.
Comment #2
Posted on Aug 12, 2009 by Quick ElephantThanks a million.. this is a huge step forward if you think of all the possibilities
Status: Fixed
Labels:
Type-Enhancement
Priority-Medium
Component-Logic
Milestone-Release1.1