This works in conjunction with the setting in AlphaValue. DefaultOnHover Default: 0Ĭontrols the transparency of the skin when the mouse is moved on and off of it. When changed using the Transparency setting in the Manage interface, a range of percentages is offered, but corresponding numeric values are stored. To have a skin be invisible but react to the mouse, a minimum setting of 1 should be used here. Note: A setting of 0 (fully transparent) will not allow detection of the mouse on the skin, and the OnHover option will have no effect. Valid values range from 0 (fully transparent) to 255 (fully visible). The !Show bang must be used to show the skin. To disable snapping temporarily, hold the CTRL key down while moving the skin. If set to 1, the skin will snap onto screen edges and other skins when moved. If set to 1, the skin can be dragged around with the mouse. Using Stay Topmost can overcome this, but again, you must not have two skins set to Stay Topmost that overlap. Note: If another application window explicitly sets itself to "top" after a skin set to Topmost is loaded, the application window will be in front until the skin is clicked or refreshed. Overlapping skins with the same setting should use LoadOrder to control relative position. Two Rainmeter skins both set to On Desktop will not change relative to each other on click. The skin will stay visible when showing the desktop and stay behind other normal application windows. DefaultAlwaysOnTop Default: 0ĭefines the Z-position (front to back) of the skin. If set to 1, changes to the window position will be saved to Rainmeter.ini. If a letter R or B is added to AnchorX or AnchorY, then the position is relative to the right or bottom edge of the window.Īs an example, by setting WindowX, WindowY, AnchorX and AnchorY all to 50% the config will be truly centered in the primary monitor regardless of screen resolution or aspect ratio. The Anchor can be defined in pixels from the upper left corner of the window or as a percentage of the config if % is used. AnchorX and AnchorY allow that anchor position to be changed. DefaultAnchorX, DefaultAnchorYīy default WindowX and WindowY control the position of the upper left corner of the config window. The screen selection will apply to both WindowX and WindowY if the value is set on only one of them. You can override this with N where N is 0 to 32 and denotes which screen to position the skin on (1-32) or the virtual desktop (0). The % and R / B modifiers can be used together.īy default the position is relative to the primary screen. A trailing B will make the position relative to the bottom edge of the screen instead of the top. A trailing R will make the position relative to the right edge of the screen instead of the left. A trailing % sign indicates that the value is a percentage of the screen width. These options will be unwieldy and clutter up your skin code if used to position several related skins. If you have multiple skins in a "suite" of related skins, and want them to all be loaded at once, with starting positions and other settings that you define, it is recommended that you continue to use a Layout in your. If you want a skin to for instance be centered on the screen, and STAY centered on the screen, this should be done with Skin !Bangs, so the position is set each time the skin is loaded or refreshed. These cannot not be used to persistently force a particular setting for a skin. All variants share a single section in Rainmeter.ini, and all settings for that. These options cannot be used to control a single variant in a config folder containing several. ini level, but actually control values Rainmeter will use at the level in Rainmeter.ini. These option are set at the individual skin. In order to have these values be used again, the end-user would need to entirely remove the section from their Rainmeter.ini, refresh Rainmeter, and reload the skin. After that, the end-user has full control over the position and all settings for the skin, as usual. The idea is that these are default / starting values to be used the first time the skin is loaded. If the already exists in Rainmeter.ini, these values are entirely ignored. Once used, they will be set as the persistent values for the in Rainmeter.ini. These option values will be used for the skin if the section does not exist in Rainmeter.ini. This will provide a way to have starting values for these settings, without having to create and distribute a Layout, or use Skin !Bangs to force a starting position or other behaviors. These options allow you to set default / starting values for the options in Rainmeter.ini.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |