Hi A B,
did you reapply your changes to the original fluent themes?
You might have to download the latest Theme Builder from here:
Best regards
Frank
Hi Frank,
I have updated to the latest nuget packages (4.1.0-beta.41) and the switch still appears the same. I have cleared the bin and obj folders, cleaned the solution and rebuilt but unfortunately have not had any success in seeing the fixed checkbox/switch. Please advise if I need to try anything else!
Thank you!
Hi A B
issue around switch appearance in Fluent Themes is fixed in Wisej.NET 4.1.0.beta41 (on nuget.org).
Best regards
Frank
Hi Alaa,
Resolution is 1920×1080 and scaling is 100% based on windows display settings. The artifacts were only happening when using a proprietary font type (unfortunately, I’m unable to share the font ttf file). I have switched to a different font and resolved that issue.
However, the switch issue in dark mode is still present after updating to the latest beta (4.1.0 beta 40).
Thank you!
Hello,
Would you please tell us the screen resolution you have and the scale settings?
We couldn’t reproduce the artifact that you mentioned!
Best,
Alaa
I owe an apology for the false report. After further investigation, I confirmed that Wisej 4.0.13 does not have this issue.
We always deploy with -r linux-x64, but it appears there was a stale cache or some other local issue on our end that caused the problem. Sorry for the noise.
Deploy net#.0 without -windows.
When you minimize a window, it hides it and changes the WindowState to minimized.
The window is still as you say “in limbo and using resources” it is not destroyed.
Note that you can have a hidden window that is not minimized.
You can still access the window after it has been minimized. There are 3 ways to do this:
1. Use the desktop template
2. Use a taskbar https://docs.wisej.com/extensions/extensions/taskbar
3.Create your own custom code that deals with the window, something like this:
if (window.WindowState == FormWindowState.Minimized)
{
window.WindowState = FormWindowState.Normal;
}
See attached test case for an example of the custom code.
Hi Julie,
My apologies, please see the test case attached.
Thank you!
Can you please attach a small reproducible test case as per https://wisej.com/support/question/forum-guidelines
Delete the bin and obj folders before posting. We will try to reproduce from your test case and go from there.
Thanks,
Julie
Hi Rene,
we still cannot reproduce the issues that you reported.
Can you please try running your sample in a different browser or in incognito mode in Chrome to see if that makes a difference?
Best regards
Frank
Hello,
There are a couple of things that could be causing this issue and it’s hard to say for sure which one without seeing a test case. If none of these work, please upload a simple test case that reproduces the issue and I’ll have a look.
Try these things:
1. It could be a clean/rebuild issue, caused by renaming the project or changing the namespace. To fix it, delete the bin and obj folders, then rebuild.
2. Verify that Program.cs looks like this:
namespace SeaPass
{
static class Program
{
[STAThread]
static void Main()
{
Application.MainPage = new MainPage();
}
}
}
3. Open the .csproj file and confirm that the AssemblyName is SeaPass.
4. Verify that your default.json looks like this:
{
"url": "Default.html",
"startup": "SeaPass.Program.Main, SeaPass"
}
5. It could be an IIS issue, might be loading an old DLL. Try this: Stop app pool, deploy, delete old files, start app pool again
Hope this helps,
Julie
Adding a second web.config file in the Pdfjs subfolder works. We put our application webconfig back to the original state and removed the static content section from it to move it to a 2nd webconfig.
This is what the 2nd webconfig file inside the pdfjs subfolder looks like:
<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
<system.webServer>
<handlers>
<remove name=”json” />
</handlers>
<staticContent>
<remove fileExtension=”.mjs” />
<mimeMap fileExtension=”.mjs” mimeType=”application/javascript” />
<remove fileExtension=”.wasm” />
<mimeMap fileExtension=”.wasm” mimeType=”application/wasm” />
<remove fileExtension=”.ftl” />
<mimeMap fileExtension=”.ftl” mimeType=”application/octet-stream” />
<remove fileExtension=”.json” />
<mimeMap fileExtension=”.json” mimeType=”application/json” />
</staticContent>
</system.webServer>
</configuration>
Hi Edmond,
by commenting out that line you’re exposing your default.json settings file and any other json files that you might have and that contain sensitive data.
I’d recommend to either add a second web.config inside the pdf folder with the json or allow just that one specific json file in your main web.config.
Best regards
Frank
Hi Julie,
Thanks for checking.
I’m using Wisej 4.1.0-beta.39 (runtime build 4.1.0.39), on .NET Framework 4.8.1, running under IIS Express, tested in Chrome on Windows. It’s the same sample I sent you, with the NuGet package set to 4.1.0-beta.39.
I’ve attached a video showing it: I first switch between several themes and perform a few actions — those respond fast. Then I switch to the Fluent theme and you can see the response becomes clearly slower for the same actions.
Steps in the video: build & run the sample, use the dropdown at the top to switch themes, and interact with the controls after each switch to compare the responsiveness.
Please let me know if you need anything else to reproduce it.
Thanks
Hello,
I tested with your sample and I am unable to reproduce. What version of Wisej are you using? Can you attach a video of you reproducing the issue?
Thanks,
Julie
For Wisej 3.5 you need to target net48 to get the designer to work, However, that is no longer necessary in Wisej 4.0.
You can use ..NET 8 9 or 10 in visual studio 2026. Your TargetFrameworks in your .csproj should look like this: net9.0-windows;net9.0 The -windows target is necessary for the designer to work.
For resolving the “WisejHandler not found” error, try to create a brand new Wisej 4 .NET 8, 9 or 10 project and compare its Program.cs and csproj to your old project. If that doesn’t work, attach a small test case the reproduces the issue and we can take a look.
Hope this helps,
Julie
Please contact support at supportATiceteagroup.com. We cannot publish this information on the internet, but would be happy to assist you there.
Thanks Frank.
As a temporary workaround, I used a JavaScript MutationObserver to replace the incorrect Portuguese translation "Claro" with "Limpar" when the filter popup is created.
Example workaround:
private void Window1_Load(object sender, EventArgs e)
{
LoadData();
dataGridView1.AllowColumnFilter = true;
this.Eval(@"
const observer = new MutationObserver(function() {
document.querySelectorAll('a').forEach(function(a) {
if (a.textContent.trim() === 'Claro') {
a.textContent = 'Limpar';
}
});
});
observer.observe(document.body, {
childList: true,
subtree: true
});
");
}
I am also attaching a small Wisej 4 sample project in case it helps others reproduce the issue.
Hopefully this helps anyone facing the same Portuguese translation problem until the official fix is included in the next Wisej.NET release.
Regards, Paul
Hi Ruben,
it should be clear.Text in SimpleColumnFilterPanel.pt.resx
We will change it for the next Wisej.NET releases.
Best regards
Frank