Hi Ed,
a server is either a physical or virtual machine and requires 1 license.
You can run any number of applications on that server at no additional license costs.
You can find more detailed information and the current prices here:
https://wisej.com/support/question/licensing-model-and-costs
Hope that helps.
Best regards
Frank
Thanks, it’s an issue that has to be solved in the themes. The inner message panel doesn’t have a right margin. It’s WJ-7418.
Hi Alex,
The groupbox in Wisej is composed of a widget container, an inner frame for the border, a checkbox (the label) and a collapse button. The problem is that the label (checkbox) shouldn’t have a transparent background when overlapping the frame (some themes may have the label above the frame). Internally, the label (a checkbox widget) automatically inherits the color of the groupbox and the groupbox automatically inherits the color of the parent. It’s done like that to create the broken line at the top. We couldn’t use the “frameset” element because of the checkbox and because it’s hard to style properly – it doesn’t support css consistently.
Best,
Luca
Hi Alex,
I can’t reproduce the second state (white background). The checkboxes use svg images from fontawesome, icons-8 and google material and the inner section is hollow. It should always show the background behind it. We can force the background of the icon widget only to be “@window” (usually white). See attached screenshot of how it would look like.
About the three state checkbox, Wisej checkboxes are two state by default. You can enable the three state mode using using the checkBox1.ThreeState property. In that case clicks cycle the three states. The Checked property would still be true when checked and false in all other cases. You can retrieve/set the Indeterminate state setting checkBox1.CheckState.
Best,
Luca
The .. promised attached pics
A
Hi Luca,
I was able to use the Tools property in a panel header now. I just didn’t assign any image/imagesource the first time I used it before.
It’s a very nice feature and can’t wait to use this in edit controls.
Thanks.
That was it – sorry I thought I had looked everywhere.
Thanks again
Nic
The Tools property is fully implemented and wired to the server events. You can use it on windows/forms, panels and splitpanels (when the ShowHeader property is true).
It just has to be integrated with the edit controls.
Best
Luca
Hi Nic,
Look at AssemblyInfo.cs. There is the WisejResources attribute. It marks the assembly. The designer and the resource manager bundle all the embedded js and css files into wisej.js and wisej.css, then minify (when not in debug mode).
We’ll have the project templates for the extensions soon.
Best,
Luca
Hi Luca,
I’ve seen that property before but can’t figure out what is that for. I understand now that it is still a work-in-process and hoping to see that working before the release date.
Thanks.
It’s in the works. The container is there already. See the Tools property of a form or a panel. You can add tool buttons to the caption.
The same container will be added to all editable controls. Same functionality and event.
Best,
Luca
Hi Luca
It’s working.
Thanks
Hi Luca,
Tested with a Blue-1 theme and it looks perfect now. Will try WinMerge.
Thanks.
Yep. Sorry about that. The designers for the DGV columns and the TreeView have been changed a lot after that fix and ended up reverting it. Now the designers are live, meaning that when you edit columns or tree nodes the changes are reflected immediately in the designer.
Anyway, there is a refreshed build available with this fix refixed. 🙂
Hi Luca,
Thanks, I have it working now. Yes, it was just a bit of XML blindness in the web.config that I didn’t catch when you posted it originally. Now working fine.
Just for a heads up, I copied the published files across to a embedded debian system running mono + xsp4. Although it attempted to run, it did fail to start with a:
“Missing method System.Web.HttpContext::get_IsWebSocketRequest()” – which looks like it is still missing out of the current mono source. So what you mentioned earlier about compatibility with mono is true at the current time.
Regards,
Mark
Hi Cris,
You shouldn’t have to redo the theme. The json files are easy to merge with tools like WinMerge. In this case the change is limited to the tree item appearance. The indent value is the same as the tree file and it has a new left padding value.
HTH
Best,
Luca
Hi Luca
Yes. The theme file I’ve been playing with is the culprit.
The changes you made on the theme are not in the custom theme yet. I can still recall, at one point, you also made changes to the themes and I had to restart all over again in creating a custom theme. If case like that, is there an easy way I can include into my custom theme changes like these without starting over again based on revised theme?
And based on the images shown above, they look OK now.
Thanks
Hi Cris,
The indentation issue was fixed in the themes. Maybe you are using a custom theme? It was a missing padding and the indent was too large on tree items. The tree nodes are themed with two different appearances, one for tree folders (with children) and one for tree items.
I tried your sample to make sure, see my screenshot:

The problem is web.config. It seems that you changed the handlers and modules inside system.webserver. That’s for the integrated pipeline and it’s not recognized by cassini. The classic pipeline settings are in system.web:
<?xml version=”1.0″?>
<!–
For more information on how to configure your ASP.NET application, please visit
http://go.microsoft.com/fwlink/?LinkId=169433
–>
<configuration>
<appSettings>
<add key=”Wisej.LicenseKey” value=””/>
<add key=”Wisej.DefaultTheme” value=”Blue-1″/>
</appSettings>
<system.web>
<httpRuntime targetFramework=”4.5″ maxRequestLength=”1048576″/>
<compilation debug=”true”></compilation>
<httpHandlers>
<add verb=”*” path=”*.wx” type=”Wisej.Core.HttpHandler, Wisej.Core” validate=”false”/>
<add verb=”*” path=”*.wx/*” type=”Wisej.Core.HttpHandler, Wisej.Core” validate=”false”/>
</httpHandlers>
<httpModules>
<add name=”Wisej” type=”Wisej.Core.HttpModule, Wisej.Core”/>
</httpModules>
</system.web>
<system.webServer>
<modules>
<add name=”Wisej” type=”Wisej.Core.HttpModule, Wisej.Core”/>
</modules>
<handlers>
<add name=”wisej” verb=”*” path=”*.wx” type=”Wisej.Core.HttpHandler, Wisej.Core”/>
</handlers>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength=”1073741824″/>
</requestFiltering>
</security>
<defaultDocument enabled=”true”>
<files>
<add value=”Default.html” />
</files>
</defaultDocument>
</system.webServer>
</configuration>
Hi Luca,
I’m just using the project from this thread:
https://wisej.com/support/question/animated-gif-in-picturebox
This is the web.config:
<?xml version=”1.0″?>
<!–
For more information on how to configure your ASP.NET application, please visit
http://go.microsoft.com/fwlink/?LinkId=169433
–>
<configuration>
<appSettings>
<add key=”Wisej.LicenseKey” value=””/>
<add key=”Wisej.DefaultTheme” value=”Blue-1″/>
</appSettings>
<system.web>
<httpRuntime targetFramework=”4.5″ maxRequestLength=”1048576″/>
<compilation debug=”true”>
<assemblies>
<!–
Add additional components here:
<add assembly=”Wisej.Web.Ext.JustGage”/>
–>
</assemblies>
</compilation>
</system.web>
<system.webServer>
<modules>
<add name=”Wisej” type=”Wisej.Core.HttpModule, Wisej.Core”/>
</modules>
<handlers>
<add verb=”*” path=”*.wx” type=”Wisej.Core.HttpHandler, Wisej.Core” validate=”false”/>
<add verb=”*” path=”*.wx/*” type=”Wisej.Core.HttpHandler, Wisej.Core” validate=”false”/>
</handlers>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength=”1073741824″/>
</requestFiltering>
</security>
<defaultDocument enabled=”true”>
<files>
<add value=”Default.html” />
</files>
</defaultDocument>
</system.webServer>
</configuration>
I must be doing something daft :o(
