When you are working on a skin you can use this trick to automatically refresh the skin when you hit CTRL+S.
That means the .ini file will save and then the skin will refresh.
Immediately presenting you with the changes that you've made, saving you the trouble of right clicking the skin and clicking refresh all the time.
[HotkeyRefresh]
Measure=Plugin
Plugin=HotKey
HotKey=CTRL s
KeyUpAction=[!Refresh]
But you cannot (at least in my case) disable the measure nor use UpdateDivider=-1 when not using it.
So just (un?)comment the line ,HotKey=CTRL s, to break it ^^
StArL0rd84 wrote: ↑March 23rd, 2019, 8:20 am
But you cannot (at least in my case) disable the measure nor use UpdateDivider=-1 when not using it.
So just (un?)comment the line ,HotKey=CTRL s, to break it ^^
Example:
;HotKey=CTRL s
Yep, you can't indeed through a !DisableMeasure bang, but there is another approach. You have to use a !CommandMeasure bang:
To disable the measure use the following bang: [!CommandMeasure "HotkeyRefresh" "Stop"].
To re-enable it, use this one: [!CommandMeasure "HotkeyRefresh" "Start"].
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
Mor3bane wrote: ↑November 30th, 2019, 3:05 am
Well if you are speed-coding and fine tuning it may simply be expedient to do this:
MouseoverAction=[!Refresh]
Not a very good idea in my opinion, because if you add the above option to a meter (or even worst to the [Rainmeter] section), the skin is refreshed every time you're hovering the mouse over the meter (or over the skin). Too frequent refresh in most cases.
As much a s possible the refresh should be avoided: https://forum.rainmeter.net/viewtopic.php?f=5&t=22739&p=119966&hilit=refresh+balala+destructive#p119966
balala wrote: ↑November 30th, 2019, 7:08 am
Not a very good idea in my opinion, because if you add the above option to a meter (or even worst to the [Rainmeter] section), the skin is refreshed every time you're hovering the mouse over the meter (or over the skin). Too frequent refresh in most cases.
As much a s possible the refresh should be avoided: https://forum.rainmeter.net/viewtopic.php?f=5&t=22739&p=119966&hilit=refresh+balala+destructive#p119966
For development, you don't need to worry about that though. It's awful for a production launch but it's not hard to just remove a single line of code. (which you'd have to remove anyway with the hotkey method)
