In my environment, I could have multiple "base" forms that are launched independently based on user need. As a result, I have multiple forms that need to share a Krypton Manager/Palette. Also, during development I noticed that a modified Krypton Palette caused my designer file to become much larger and it also slowed my form load times. To resolve this I moved both the Manager and the Palette to a form that does nothing other than act as a container.
When in design time, any settings I have changed on the Manager/Palette (such as defaulting it to Office 2007 Silver) do not apply to other base forms until the container form (KryptonPaletteForm) has been opened. The KryptonPaletteForm can be closed and VS will remember your settings.
To make the KryptonPaletteForm function at runtime you need to load the Manager/Palette into memory so your form will use it's settings. I do this by creating an instance of the form in the constructor of main form I am loading. Example:
- Code: Select all
Public Sub New()
Dim kryptonPaletteForm as New KryptonPaletteForm()
InitializeComponents()
End Sub
Creating the instance is all I've needed to do to make this work. Hopefully this explanation helps you to understand. Let me know if you have any questions.