- Merged Rainmeter.dll and Rainmeter.exe
- Language resource file now located in \Language\<LanguageName>.dll
- Build.bat now automatically builds and packages all languages
Changes to multiple files to change version number
Changes by JamesAC / spx to improve management of Windows Mssages, mostly to support working with the DexPot folks
Addition of the Win7AudioPlugin plugin by reiswaffle. This includes plugin code and changes to the Rainmeter.sln project file.
This commit is to get the repository set up to add Rainstaller.exe to the Rainmeter build and installation package
- Rainstaller is installed to the Rainmeter program folder under \Addons\Rainstaller
Rainstaller.exe
Rainstaller.chm
- A file association is created for the extension .rmskins to allow double clicking a .rmskins file to open Rainstaller.exe, unpack the .rmskins archive (it is a renamed .zip file) and install the Skin(s) / Themes included.
- Rainstaller.lnk (Rainstaller.exe) and Rainstaller Help.lnk (Rainstaller Help.chm) are added to the Windows Start Menu under Rainmeter
- Code added to the "uninstall" routines in Rainmeter Install Script.nsi to remove the file association for Rainstaller.exe / .rmskins on uninstall of Rainmeter and to remove the links from the Windows Start Menu.
*****************
Code Changes:
- New version of Build.py for compiling all source code
- New version of Rainmeter Install Script.nsi for creating the Rainmeter installation package
- Source code and build script for Rainstaller in \Addons\Rainstaller\Source
Rainmeter.nsi
Rainmeter.chm
\include (folder has some addon scripts and plugins for NSIS)
Note: As of this build, everything works EXCEPT that Rainstaller can only be used by double-clicking a .rmskins file. The ability to drag and drop a .rmskins file on Rainstaller.exe or to run Rainstaller.exe and "browse" to open a .rmskins file is coming in the next day or two.
Rainy, given the "issues" listed at the bottom of this comment, I leave it to you whether to create a build using this revision or use r208 for the build. I would like to start testing MeterStyle, but there are a few more things it needs work on.
What is MeterStyle?
MeterStyle
This will allow users to create CSS-like "Styles" for meters. This means that all the parameters of a meter can be defined in the style, and then many meters can use the style to eliminate copy / pasting the same parameters over and over on multiple meters. (Examples: FontColor=, FontSize= etc.)
How do I use it?
You will create a new [Section] (as many as you want) in the .ini. The section(s) can have any name.
[MyStringStyle]
Then you will tell Rainmeter that this is a "MeterStyle" and not a measure or meter
Style=Meter
Note: The "value" of the key "Style" can be anything. It can be used to add a description of the style if you like. Style=This style is for the AccuWeather part of this skin
It is however required, both to tell Rainmeter it is not a meter or measure and to have the MeterStyle routines parse it.
Then you define parameters you want to use in the style
FontColor=#FontColor#
FontFace=TheSansBold-Caps
FontSize=11
StringEffect=SHADOW
StringStyle=BOLD
StringAlign=LEFT
AntiAlias=1
Then in any or all meters, you just use
[MeterName]
Meter=STRING (or any other meter type)
MeterStyle=MyStringStyle
None of the parameters in the style are then required to be actually in the meter(s). They are "inherited" from the MeterStyle.
Note: This works and has had preliminary testing with dynamic variables like FontColor=[MeasureName] and regular variables like FontColor=#FontColor#. It doesn't matter if the [Variables] section or the [MeasureName] measure is before or after the [StyleName] in the .ini file.
What if I want to override a MeterStyle parameter on a meter?
Sure. Just put in any parameter with a value different from the one defined in the MeterStyle and the one in the meter will take presidence. All non-defined parameters will still use the MeterStyle value.
[MeterName]
Meter=STRING
MeterStyle=MyStringStyle
FontColor=100,100,100,50
What are these "known issues" you are on about?
This is still a bit of a work in progress. Right now you cannot define X or Y in a style. You can define W and H, but NOT for a STRING meter. You cannot define a "Transformation Matrix" in a style. MattKing will be looking into these tomorrow. W and H in a string meter is our top priority. We will also look at X and Y and hope for an easy solution. Transformation Matrix may have to come later.
