Refreshing the skin (doesn't matter how, manually or through a bang) is the simplest way to get the variables re-read, but as you figured out, this in fact rebuilds the whole skin. Every dynamic change (done by !SetVariable or !SetOption bangs) is lost. There are some details related to refresh here.The first post is no longer important, I have already moved on and do not want to return to it and my only question is, is there a single command for the skin to re-read the values specified in the ini files? I need Variables, of which there are several dozen, to again take the values specified in the ini. Or set the values for each variable manually again? Or at least how to do something like !ReadKeyValue from a file?
Another way is to manually set proper values for the variables. You can use a LeftMouseUpAction option on a meter, for instance something like this: LeftMouseUpAction=[!SetVariable Hp "81"][!SetVariable ip "81"][!SetVariable Tp "81"]... (obviously this is just an example, I don't know which variables you have to re-read, but for these I added the values set in the Settings.inc file). When you click the meter, all variables listed there get the values set in this option. If you take care to add their initial values, in fact you get them set to their original values, so it's like they should have been re-read.
Alight, now I realize what did you mean by blink. Yep, especially when refreshing large skins, you can get it blinking. There is nothing you can do on this. Smaller skins usually are not blinking, but larger ones do.The !Refresh command does this, but it refreshes the entire skin and it blinks while doing so.
Refreshes, as much as possible should be avoided. In some cases it has to be done, however as much as possible it is preferable to be omitted.I got out of the situation by using !Refresh which is started by a timer before the transition through zero hours. But if suddenly the refresh period is set too long, the trick will not work. It would be possible to refresh every time, but the skin blinks during the refresh. Once at zero hours is not so bad. I also set a refresh when exiting sleep, so that the problem would not arise if in this case there was a transition through zero. Setting the meter coordinates again is somehow too crooked, and I do not know how they can be calculated from the ini.
Which invisible elements? On refresh there are some elements going outside of the skin, but once the data are got from web, there is nothing shown outside of the black background rectangle. If this is what you'd like to avoid, I recommend to set a proper size for the skin, by adding a SkinWidth and a SkinHeight option to the [Rainmeter] section. For example:I still need to move the invisible elements inside the skin, I don't know yet how best to do this
Code:
[Rainmeter]...SkinWidth=602SkinHeight=312...
Statistics: Posted by balala — Today, 7:01 pm