CyborgTJB wrote:Whenever I unload it rainmeter stop working.
I don't see anything in your code, which would crash Rainmeter, once you unload the skin. And when I tried them, my Rainmeter didn't stop working.
However three general observations:
Update=1? The lowest possible value of the Update is 16 (read the second paragraph here).
Try to add a DynamicVariable=1 option to each section where the #SCREENAREAHEIGHT# and #SCREENAREAWIDTH# variables are used. Although this settings need to be used just when the measures should detect changes, maybe you could try this setting, to see if it helps.
Don't use the !Rainmeter bang prefix. Replace the !RainmeterMove bang, with the newer !Move. See that the !Rainmeter... prefix is deprecated.
You know what forget my code. I had it from the beginning.In win7-crash, in win 8and 8.1-crash and win 10-crash. Same.
I really doubting my knowledge of rainmeter from this one.
Can you make a new one just like this...(with extra feature) with new rainmeter bang and updates?
(no preasure)
Exactly. Or far better, I'd use the following form: IfEqualAction=[color=#FF0000][[/color]!Move [color=#FF0000]"[/color][MeasurePositionX][color=#FF0000]" "[/color][MeasureMove][color=#FF0000]"][/color]. Note the newly introduced characters. Although you can waive them, usually is a good idea to get used using them.
Both the !Rainmeter... bang prefix and the !Execute bang was deprecated long time ago, that's why you don't have to use them. They also work, but just for compatibility reasons.
CyborgTJB wrote:This and "Update=16". Looking smooth now buddy.
But what about your initial question? That about crashing Rainmeter, when you unload the skin.
For me that's not happening with the skins you've uploaded. Both work well, however I have the same observations, I wrote above: Update=1 is too small, you should replace it with (at least) Update=16 and the !Rainmeter... prefix should be removed.
balala wrote:But what about your initial question? That about crashing Rainmeter, when you unload the skin.
For me that's not happening with the skins you've uploaded. Both work well, however I have the same observations, I wrote above: Update=1 is too small, you should replace it with (at least) Update=16 and the !Rainmeter... prefix should be removed.
My guess is, he is trying to create some scanning effect using these 2 .ini files. When you load both .ini files Rainmeter crashes. I think that's what he means. Besides that every skin at its own runs as expected.
kyriakos876 wrote:My guess is, he is trying to create some scanning effect using these 2 .ini files. When you load both .ini files Rainmeter crashes. I think that's what he means. Besides that every skin at its own runs as expected.
Well, I didn't thought to this possibility to load both skins simultaneously, CyborgTJB didn't mention this (or I missed something?).
However, my Rainmeter doesn't crash, neither with both skins loaded, neither when I unload one of them (any), or both.
But if you're right and CyborgTJB indeed would like to create a "scanning effect" with the two skins, in my opinion would be better to unify the skins, into one single.
Let's see what CyborgTJB will say...
balala wrote:Well, I didn't thought to this possibility to load both skins simultaneously, CyborgTJB didn't mention this (or I missed something?).
However, my Rainmeter doesn't crash, neither with both skins loaded, neither when I unload one of them (any), or both.
But if you're right and CyborgTJB indeed would like to create a "scanning effect" with the two skins, in my opinion would be better to unify the skins, into one single.
Let's see what CyborgTJB will say...
No CyborgTJB never mentioned this I just happened to load them both and while they were both loaded, I try to unload the first one and Rainmeter crashes, leaving no error message in the log. But yea.. let's wait for a reply.
