Added the Classic-2 theme. It has metrics similar to VWG. The problem with going from VWG to Wisej is that VWG messed up the size/client-size of forms.
In VWG the form sets and serializes Size instead of ClientSize.
It also applies the Size as if it was the ClientSize and enforces MinSize and MaxSize on the client instead of the overall size.
Wisej preserves the ClientSize and enforces MaxSize and MinSize on the overall size, which is the correct implementation.
To go from VWG to Wisej without messing up the size of a form, regardless of the theme:
– Replace all this.Size to this.ClientSize in Form.desiger.cs/
– Either remove or recalculate MinSize and MaxSize to enforce the overall size.
Actually the themes definition docs are there:
Update Classic-2 theme with active state
Update Classic-2 theme with active state
Inactive caption:
In Windows 10 I get the same white caption, only the thin border and the title text change color when inactive.
In any case, that is easy to personalize with a mixin.
{
"colors":
{
"inactiveCaption": rgb(1,2,3)
}
}
I just typed this so I’m not sure it works and the rgb() color is a placeholder. You can use the #rrggbb or rgba() formats as well.
Make a custom theme available to multiple projects:
Good question. Custom themes are single files that the project needs to find somewhere. You can either copy them in the /Themes folder (in which case the folder and the theme must be deployed), or you can make your theme become an embedded resource in your shared assembly and it will be available to all the projects that use that assembly.
In the shared assembly, make the theme file become an “EmbdeddedResource” and ion AssemblyInfo.cs add
using Wisej.Core; [assembly: WisejResources()]
I haven’t tried this in a while as well. Will try next and let you know if I got it wrong.
One issue:
One question:
It’s available on the themes download page.
Please login first to submit.