Export to GitHub

rainmeter - issue #118
!RainmeterDeactivateConfig on self does not change Active= value.
Posted on Oct 17, 2009 by
Quick Wombat
Discovered while testing the fix in r277. If a skin deactivates itself by an IfEqualAction, etc., the skin does close, but the Active= value in Rainmeter.ini does not become 0.
Comment #1
Posted on Oct 18, 2009 by Quick RhinoAlthough I also tested, it was correctly set as 0.
Comment #2
Posted on Oct 18, 2009 by Swift CamelThere was a timing problem. If the skin deactivated itself immediately on the first update it was marked as active after the deactivation was already handled. This is fixed now in r283.
Status: Fixed
Labels:
Type-Defect
Priority-Medium