All Answers

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

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

Hi Tamas,

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

Best regards
Frank

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.

Hi Paul,

Try clearing the Designer Cache.

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

Best,
Alaa

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?

Hi Pavel,

you might want to try adding

dropDuplicateClicks = true

to your default json. If that is not enough you could disable the button while your handler is running and reenable it at the end or add a busy flag that you can check.

Best regards
Frank

Attaching sample code…

Browsers don’t let you change the zooming level programmatically. It’s not a wisej issue.

Also browsers don’t react on dpi. You can change the app layout to be proportional using anchoring, docking, etc.

You can see a list of open issues and recently fixed bugs here: https://wisej.com/issues/

Anything listed as 3.5.xx is also fixed in 4.0.xx. For example, “Designer fails to display any control due to a recent windows update breaking all internal http listeners” says 3.5.32 but it was also fixed in 4.

Anything beginning with “Wisej.Net 4” is fixed only in 4.0.xx. For example, “Wisej.NET 4 – Image Editor does not keep the previous selection” was an issue specific to Wisej.Net 4 and so it was only fixed there- not in 3.5.xx.

It’s not a crash. It’s an exception that a class cannot be cast to an interface. It means VS loaded multiple versions of the same assembly, which means you have multiple versions of Wisej.NET in the same project or an installation that is wrong. Delete all .bin and all .obj, uninstall all installations of wisej, search for any Wisej.Core and Wisej.Framework dlls and make sure the machine is clean. Install Wisej 4 extension and it will work.

Otherwise try on a clean machine.

And a screenshot of the nugget package. It has other version.

Hi Frank, thanks a lot for your response.
I have procceded with the below acrions.

Uninstall from the VS extenions all Wisej products.
Restart the pc.

Fresh install using https://www.youtube.com/watch?v=8BTvHicJesc instructions.

After installtion finished, i have created a new wisej web aplication. When i open the designer same error occured.
Sending also screenshoots.

Thanks
GA

Hi Paul,

most of this is under control of VisualStudio and beyond ours.
What I noticed is that once the Toolbox is working, leaving at least one designer file open seems to keep it working.

Best regards
Frank

Hi,

thanks for reaching out. Please contact us at support@wisej.com with your company and license details and we’ll discuss it from there.

Best regards
Frank