torenaughty.blogg.se

System monitor rainmeter
System monitor rainmeter












System monitor rainmeter skin#

The Skins folder can also be changed in Rainmeter's settings.Ī skin is stored as a named. SkinName.ini in its own named folder within Skins, as in: Rainmeter\Skins\ SkinFolder\ SkinName.ini.Īll of these folder paths may be referenced in a skin as built-in-variables. If a single folder contains multiple SkinName1.ini, SkinName2.ini. files, they are each considered variants of the same skin. Only one variant can be active at a time, and all variants use the same settings. Separate skins not to be treated as variants must be stored in separate folders.Ĭ:\Users\YourName\Documents\Rainmeter\Skins\illustro\Clock\ 12HrClock.iniĬ:\Users\YourName\Documents\Rainmeter\Skins\illustro\Clock\ 24HrClock.iniĬ:\Users\YourName\Documents\Rainmeter\Skins\illustro\ 12HrClock\Clock.iniĬ:\Users\YourName\Documents\Rainmeter\Skins\illustro\ 24HrClock\Clock.ini supporting files used by the skin, such as images, addon executables, sounds, or Lua scripts, should also be stored in the skin folder. Complex skins are recommended to store supporting files in a folder called inside the root config folder. The folder is used by Rainmeter to load custom fonts and custom cursors. ConfigĮach skin is identified with a certain config name.

system monitor rainmeter

The config name is based on the path from the main Skins folder to the skin file. For example, if a skin is located at.Ĭ:\Users\YourName\Documents\Rainmeter\Skins\ illustro\Clock\Clock.iniīecause skins may have any number of variants, many Rainmeter features, especially bangs, refer to a specific skin by its config name, rather than the skin's filename. Skins may also be stored in subfolders within the same root config folder. They share the same folder, and are packaged and installed together. This means that they are both located in the same root config folder, "illustro," in the main Skins directory.Ĭ:\Users\YourName\Documents\Rainmeter\Skins\ illustro\ Otherwise, Rainmeter treats each subfolder as a separate config.įor example, the following skins belong to the "illustro" suite:Ĭ:\Users\YourName\Documents\Rainmeter\Skins\ illustro\Network\Network.ini

system monitor rainmeter

The root config folder for a skin will ALWAYS be directly under C:\Users\YourName\Documents\Rainmeter\Skins\. No matter how many levels of folders your suite of skins may have, there will always be a single, shared root config folder for that suite of skins, directly under the. This is where the folder must be.īut since they belong to the same root config, they share the same folder:Ĭ:\Users\YourName\Documents\Rainmeter\Skins\ suite is an informal term for skins that are organized together in this manner. Suites are often used by skin authors to make a set of skins that share a common style, or complement each other in some way. If a root config folder contains only one SkinName.ini file, then the config and root config are the same, and the skin can be stored, packaged and installed by itself. The SkinName.ini file is written as a standard INI file, which uses the following format: Įach property of the skin is defined by a section. Each key is an option that modifies that property. The following sections may be used in skins:ĭefines options that affect the entire skin.ĭefines text strings that can be used throughout the skin. Objects that retrieve (or "measure") information of some kind. Objects that display information and other visual elements.ĭefine options that may be used by several meters.ĭefines the name, version, license, and other non-functional information about the skin.Ī skin must have at least one meter.

system monitor rainmeter

All other properties are optional, and may not even be present, depending on what is needed for the skin. #Rainmeter system monitor skins skin#Īll section names in a skin must be unique.There are only a few rules about using the INI format: For skins that are publicly distributed, the section is strongly recommended. Option values must be kept on a single line.Section and option names should include alphanumeric characters only (no spaces or punctuation).All option names within a section must be unique. "Quotes" are not needed around strings used as an option value.

  • #Rainmeter system monitor skins windows#.
  • #Rainmeter system monitor skins portable#.











  • System monitor rainmeter