All Answers

0 votes

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

  • Paul answered May 8, 2026 - 4:23 pm
0 votes

Hi Ruben,

it should be clear.Text in SimpleColumnFilterPanel.pt.resx

We will change it for the next Wisej.NET releases.

Best regards
Frank

0 votes

Hi again, i must apology: my license is only vaid for one activation and i changed the Raspberry hardware and sd card so this was my problem.

0 votes

Hi Paul,

this has been reported and fixed and will be deployed with the 4.0.12 release.
As a workaround please use 4.0.12-preview2 on nuget.org

Best regards
Frank

0 votes

Hi Nico,

please send your license key to support@wisej.com and we’ll take a look.

Best regards
Frank

1 vote

Ok, with Application.Update() the enable/disable works. But as we wanted handle this globally, we resolved this by creating our own event handler which wraps the original one using reflection. And in the wrapper event we using the enable/disable.

0 votes

You can’t stop characters from the server. Use the Filter property (see docs and api) or a javscript event handler. It’s much better if you attach a zip file with the sample and runnable code. I don’t think anyone would like to type code snippets for you.

  • JD answered Apr 24, 2026 - 8:42 am
0 votes

You’re correct that the call to Application.Update does not have to happen in the ViewModel.

Here’s a sample showing how to do async commands in Wisej MVVM.

– The async method should be in the ViewModel,
– Navigation or shell swapping should happen in an application-level ViewModel reacting to authentication state
– Any Wisej-specific Application.Update(…) usage should be hidden in infrastructure that restores/pushes the Wisej context rather than called from the ViewModel itself.

– In the sample, look at:
– LoginViewModel.cs for the async login logic
– ApplicationViewModel.cs for shell swapping (MainViewModel and LoginViewModel are the shells)
– WisejAsyncCommand.cs and WisejUiDispatcher.cs for the Wisej-aware command/context handling
– WisejUIDispatcher for the call to Application.Update
– Window1.cs for the shell host.

0 votes

Dear Julie,
thanks for your answer.

So you mean in the definition of the LoginCommand in the ViewModel’s constructor:

LoginCommand = new Command(
            execute: async () => { var context = Application.Current; await LoginAsync(); Application.Update(context); },…

However I find it a bit strange, in the sense I would expect my ViewModel to be unaware of Wisej’s Application.Current etc. What if I wanted to use the same ViewModel for a WinForms application and not a Wisej one?

Best regards,
Alex

0 votes

Application.Update(this) works when this is a Wisej control. But in your case, this is the ViewModel. So don’t use Application.Update(this). Instead, you can save the context before the await by doing:

var context = Application.Current.

Then when you need to update the UI you can do:

Application.Update(context);

More information on Application.Current: https://docs.wisej.com/api/wisej.web/general/application#current

0 votes

Have you tried di define the dobleclick sub as Async and use a semaphore?

0 votes

Hi Pavel,

maybe I missed the point of your sample but if I change the code like this I don’t get any further double clicks during the processing of the double click event:

private void Button1_DoubleClick(object sender, System.EventArgs e)
{
 this.button1.Enabled = false;
 Application.Update(this);
 this.label1.Text += $"\r\nDouble click at {DateTime.Now:HH:mm:ss.fff}";
 Thread.Sleep(2000);
 this.button1.Enabled = true;
}

If this is not the intended behavior, please explain in more detail or update your sample to demonstrate it.

Thanks in advance.

Best regards
Frank

0 votes
In reply to: WiseJ + Syncfusion

Hi Tamas,

we’re exploring various options and will update you next week.

Best regards
Frank

0 votes

Hi,

After uninstall from extentions as wisej products, I did a deep search deleting all wisej dlls that i found in several folders.
After that, i install only  ver 4.0.11  and it seems to worl ok. I think that the problem occured from old  dlls that are not deleted after uninstall from all folders.

Thanks a lot for your support.
GA

0 votes

Dear Frank,

This is a very excellent approach. MCP is indeed the best solution, much like the implementation of ‘Devexpress docs mcp’. It increasingly reflects the atmosphere and standards of a major corporation. We truly appreciate the team’s hard work and dedication.

  • dev answered Apr 17, 2026 - 2:15 am
0 votes

Hi Paul,

Try clearing the Designer Cache.

That should help with the .NET Coredesigner toolbox not being loaded properly.

Best,
Alaa

  • Alaa (ITG) answered Apr 16, 2026 - 6:20 pm
  • last active Apr 16, 2026 - 6:20 pm
0 votes

Hi Frank, thanks for your response.

I removed Wisej 3 and Wisej 4 from Visual Studio 2026, then reinstalled only Wisej 4. The designer issue still occurs, but less frequently.

When it happens, I follow these steps:

  1. Close the project and Visual Studio
  2. Delete the .obj and .vs folders
  3. Reopen the project and rebuild

This refreshes the toolbox, so it works as a workaround.

Regards

  • Paul answered Apr 16, 2026 - 6:11 pm
0 votes

Hi George,

I installed Wisej in Visual Studio 2022 in the following order:

  1. Wisej 3
  2. Wisej 4

I then created a new project using Wisej 3 targeting .NET 9, and it opened correctly in the designer.

I’ve attached my test project in case it helps with troubleshooting.

Regards

  • Paul answered Apr 16, 2026 - 6:05 pm
0 votes

Unfortunately, setting `dropDuplicateClicks` didn’t help, and disabling the button or creating a flag won’t help either, because the events aren’t triggered in parallel but in sequence. Is there any other way to handle this, please?

0 votes

Hi,

we are now providing an MCP endpoint to our GitBook documentation.
See here

https://docs.wisej.com/docs#mcp-endpoint

Best regards
Frank

Showing 1 - 20 of 11k results