- This topic has 3 replies, 2 voices, and was last updated 15 years, 4 months ago by
.
Viewing 4 posts - 1 through 4 (of 4 total)
-
Posts
-
Hi there,
it seems that selecting a skin when the SkinManager is not active does not work. I added code to save and restore the previously user-selected skin name, and setting the SkinName property does not work when the Active property is false. Setting the Active property before selecting the skin causes ugly side effects due to switching the skins. Any suggestions how to change this? Or better: Could you change that behaviour?
Hi
You must define SkinName firstly and set Active to True after it.
SkinManager will not be Active if skin is not defined…
How we can improve a behaviour?” border=”0″ alt=”smile.gif” /></p>
</div><!-- .bbp-reply-content -->
</div><!-- .reply -->
<div id=)
QUOTE (Support @ Nov 26 2009, 10:19 AM) <{POST_SNAPBACK}>Hi
You must define SkinName firstly and set Active to True after it.
SkinManager will not be Active if skin is not defined…
How we can improve a behaviour?” border=”0″ alt=”smile.gif” /><!--QuoteEnd--></div>
<p><!--QuoteEEnd--></p>
<p>Well, actually it works just the other way round for me. I added a couple of skins to the internal skin store and set one of them as the default skin during design time. If I set the Active property to True, I have graphical glitches in my splashscreen, so I set it to False at designtime and only activate the skin at runtime.</p>
<p>BUT: When I set the Active:=True at runtime, my App will not show up with the skin set during design time but with the first skin in the internal list… I could imagine changing the designtime code so that the skin selection becomes disabled when Active is false. Or better: when reading the default settings at runtime, don't discard the skin name if Active is false.</p>
</div><!-- .bbp-reply-content -->
</div><!-- .reply -->
<div id=)
QUOTE (OldGrumpy @ Nov 26 2009, 11:28 AM) <{POST_SNAPBACK}>BUT: When I set the Active:=True at runtime, my App will not show up with the skin set during design time but with the first skin in the internal list… I could imagine changing the designtime code so that the skin selection becomes disabled when Active is false. Or better: when reading the default settings at runtime, don't discard the skin name if Active is false.
I'm thinking about a better solution now and this solution will be found soon, I hope.
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.