- This topic has 7 replies, 2 voices, and was last updated 7 years, 5 months ago by
.
-
Posts
-
OnDeactivate is only called if SkinManager.Active is set to False.
So, to get things straight when the skin manager is made active, OnActivate should also only be called when SkinManager.Active is set to True.
As it is now, it is not symmetric, because OnActivate is also called on a skin change. That's where the OnAfterChange event is for.
It is awkward now, because you cannot do initialization stuff when the skin manager becomes active.
'Support' wrote:This behaviour will ne changed in the next release.
Although OnActivate is now called only on activation, OnDeActivate is not called when the SkinManager is destroyed. Allocations in OnActivate will leak memory when SkinManager is destroyed.
'HeDiBo' wrote:Although OnActivate is now called only on activation, OnDeActivate is not called when the SkinManager is destroyed. Allocations in OnActivate will leak memory when SkinManager is destroyed.
Don't put too much effort into this. It's really a very minor detail.
- You must be logged in to reply to this topic.