So I'm giving up with trying to limit the gray transparency thing to just the area with text. And I figured out that even with the refresh rate down on the gadgets, they still ate into my ppd too much. At least they're loaded now and I can pull them up for gaming and/or anything network related.
But I figured that another script with a few more comments would help anyone looking to try their hand at this.
For anyone looking to modify one of these scripts for your own use, here's a crash course. Chris or anyone else, please feel free to comment.
Rainmeter Script Modifying Crash Course
I know it's more complex than this, but it seems that for this purpose, it's split into 4 areas.
Section 1 & 2
The top two are very short and setup the rest of the script. Those are the metadata and the variables. The metadata is just that, info used to identify the file for our purposes, while variables is a little misleading for anyone with C programming experience as in this isn't an area that ALL variables need to be declared, just the ones pulling info from outside sources. So here, it would be the extreme overclocking stats page and the local HFM summary page, both in url form. TextColor is also declared here and is used throughout the script.
After this is the meat of the script with the measures and the meters.
The Measures area uses the plugin WebParser.dll to analyze a webpage and allow rainmeter to read the source code of it. But it's not a magical plugin that doesn't need any help. The RegExp (or regular expression) is the backbone of how rainmeter gets it's info. For example, the first part of Chris's code (what I used as well) starts like this:
RegExp="(?siU)<tr>.*<td width=".*" class=".*" bgcolor=".*">.*<font color=".*">(.*)</font>.*</td>.*<td width=".*" class=".*">(.*)</td>.*<td width=".*" class=".*"><a href=".*">(.*)
The (?siU) basically says that webparser should search until it finds the complete expression "<tr>.*<td width=".*" class=".*" bgcolor=".*">.*<font color=".*">(.*)</td>", (the yellow
part) using .* as a wildcard so that it doesn't get confused by the text that changes with each refresh and/or user, and then copy the text following it (.*)
into string 1 (see figure code.png to get a better picture).
So then, it'll go through the first RegExp line which is for the extreme overclocking stats page and then put each one of the (.*)'s that it's told to copy, into the next string variable. NOTE: You do not have to declare the strings, they seem to be declared as they are used.
After that, it'll work on the RegExp for the HFM summary page, which is partly shown as the example above.
Finally, the last section is the meters, or basically, how the stored information can be displayed. This one's fairly straightforward with X= and Y= being the horizontal and vertical placement of that line, but with a small twist.
If you want the line or image to be displayed in one spot no matter the size of whatever's shown before it, then just use numbers. An example of this is, in my screenshot, you can see that both of my pictures (intel and nvidia) are lined up on the right. That's because I set them to stay 120 units (guessing pixels) to the right of the far left side. However, I could have done what Chris did and made their placement relative to the size of the text before it. For me, that would mean that the nvidia logo would be much further left, up against the end of "9800GT" and the intel image would move slightly left
NOTE: Although the width and height seem to be declared in the script, it seemed to have just put up whatever size I had the original image. So I'm not sure if this part is necessary or not.
Hopefully this will help someone with little to no programming experience feel a little more at home while looking at the scripts posted and maybe allow them to tailor them to their liking.
EDIT: Had a slight string number error in the client 2's ppd. Fix'd with new screen. I also found a few textures that work awesome for that third awkward monitor and using Display Fusion, I can keep all three monitors different and still rotating. Plus, stickies rule. Edited by tismon - 1/28/11 at 6:13am