New Rainmeter beta version available:

32bit: http://rainmeter.googlecode.com/files/R ... t-beta.exe
64bit: http://rainmeter.googlecode.com/files/R ... t-beta.exe

Changes:
- Changed RainThemes to automatically create a theme called "AutoSave" which will contain your current setup.
- The windows stay visible with Windows 7 Aero Peek.
- WebParser reads the resource now only if it has been modified. This can be overridden with ForceReload=1.
- !RainmeterRefresh and !RainmeterQuit are now handled only during the event loop since they can crash the application if executed during Update().
- It's now possible to use the measures as if they were variables (use [MeasureName] instead #VariableName#). Set DynamicVariables=1 for all meters and measures which refer to other measures.
- New bang !RainmeterSetVariable can be used to change the value of a variable (DynamicVariables must be 1 in places where the variable is used).
- Skin information and instructions can be added to [Metadata] section.

Here's simple example how to use the dynamic measures and variables:

First of all, thank you with chocolate and magic for the measure variables. This is going to change the way we use Rainmeter. I'll show you.

Second, I've got a big bug in the new build: Measures are not returning strings from WebParser. Debug=1 shows that the information is all being received and assigned the proper StringIndex, but nothing is being displayed. Oddly, my RSS reader shows the feed title, but nothing else - it could be that it's having a problem when other WebParser measures refer to the first one through URL=[Measure]. But this does not explain why MoxaWeather is showing nothing at all.

Update: I replaced WebParser.dll with the one from Rainmeter 1.0, and it didn't help, so this must be something in the core.

_________________
Home | deviantArt | Flickr | Enigma Support | V.I.S.O.R.

Yep, the measure references mess up the webparser's urls. I also noticed that some of the plugins are not compatible with the new feature so the dynamic variables are disabled for them now. Enabling it probably requires changes to all plugins unless I can figure out some other way to fix the issue.

Anyway, a new beta build is available from the above links.

Wow! Everything there is gold! I didn't expect all of this so soon.

_________________

|V.I.S.O.R|

A couple of problems,
when using the new build, the locations of several meters has changed, to places which do not match with what is in the ini file. Also, the meters showing total memory and total HDD space are showing massive negative values, while the values displayed in the "About" box are correct

I am running Vista SP1

_________________
Quis custodiet ipsos custodes?

Everybody loves the dropbox

Right so reporting in with stuff. As of r192

Work = X, Y, Color, Angle

NotWork = H, W, FontSize, GradientAngle

This is mostly to keep an update of what you can use Key=[Measure] for.

I not seeing any of that on mine. Also Vista SP1. Everything is working as it should although I have not check tried any of the new features. But the old stuff seems to work as it always did.

_________________

Ah

I am using exactly the same skin as before the change and have not tried any new features

This is what it looked like before:

[hsimg]http://i191.photobucket.com/albums/z20/cryptoworm/Bar1_0.jpg[/hsimg]

And this is now:

[hsimg]http://i191.photobucket.com/albums/z20/cryptoworm/Bar1_1r191.jpg[/hsimg]

_________________
Quis custodiet ipsos custodes?

Everybody loves the dropbox

GradientAngle works perfectly for me. Also, W and H work, but you have to use a formula to guarantee that they start with dimensions (ie: W=(1+[Measure]) or something).

My prediction is that anything that can't accept zero as a value will not work. Everything else seems to be working smoothly so far.

_________________

|V.I.S.O.R|

It is because uppercase and lowercase of the key name are strictly distinguished, in r189 (by changing ConfigParser::ReadString() and using stdext::hash_map).
E.g. Color=000000 is OK, but color=000000 is NG and use default.
(Is this behavior a new specification? Or, is it a bug?)