All Answers

1. I have created the attached project. I had my designer in the “Bootstrap-4” theme
When running the application, it looks as expected. Changing the theme via the button to “Vista-2” also works without any problems.
2) I change the theme in the Designer to “Vista-2” and save. Various properties in Window1.Designer.cs are now changed in the background.
When I run the program, everything still looks as expected. Switching via the button also works.
3. I change the property “Font” of Window1 via the Designer to “Theme Fonts -> default”. This corresponds exactly to the value that was previously displayed as the default. (@default; 8pt; Regular)
This adds the following line to Window1.Designer.cs
this.Font = new System.Drawing.Font(“@default”, 8F, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point);

When I run the application now, my fields are suddenly completely shifted (regardless of the theme).
In the Designer, everything looks exactly the same as before.
In debugging, you can see that the size of the fields is changed at exactly the point where the “Font” property is set.

We have not currently changed the font in our productive application, but according to the GIT repository, this line has already existed for a long time. However, the behavior is the same as in my example. It has not occurred before and has only been occurring for a few days.

Excellent, Julie!

That worked perfectly. Thank you!

1. You can attach to the onSelectionChanged event like so:
   dxLookup1.Instance.onSelectionChanged += new WidgetEventHandler(this.dxLookup1_onSelectionChanged);private void dxLookup1_onSelectionChanged(object sender, WidgetEventArgs e)
{
AlertBox.Show(e.Data.ToJSON());
   }
2. You can use optionAsync to get the value: (must be async because we expect a value back.)
   int value = await dxLookup1.Instance.optionAsync("value");
AlertBox.Show(value.ToString());
3. If you want to change the selected value via code, you can do it like so: (where 2 is the new value to be set)
   dxLookup1.Instance.option("value", 2);

See attached sample.

Can you please provide a reproducible testcase? Delete the bin and obj folders before posting.

I am a co-developer of this solution. What I have just found out is that if you press the Edge button at the bottom right of the Designer and switch to IE, the masks in the Designer are displayed correctly again. At least for a certain time.

Hi Tiziano,

Your “Protocollo.Portal” project needs to target both net9.0-windows and net9.0 for it to work as expected.

Otherwise, there’s going to be a mismatch when loading the libraries.

Best Regards,
Alaa

Thanks somuch

Hi,

it’s easy. Download the VSIX here:

https://wisej.com/builds/

And then download all packages from nuget.org just search for Wisej-4*

Best regards
Frank

Hi Tiziano,

It’s not something related to your code, but it happens only when the app is running in net9.0-windows.

If you run it in net9.0, it should work just fine.

We’ll continue to investigate the issue on our end and let you know!

Best Regards,
Alaa

Hi Luca,

thanks for your answer.

We need that library, anyway we could rewrite all the library code.

But, supposing to remove all System.Drwaing references, like I did in the screenshot and the attached code, what should we use instead of System.Drawing?

Many Thanks,

Luca

Hi Edmond,

Audio is played through browser media support. It’s beyond Wisej.NET support scope to tell if it supports to HIPPA rules or not.
Check out audio formats etc. here

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/audio

Best regards
Frank

Hi Edmond,

Wisej 3 only supports Visual Studio 2019 and 2022, Wisej 4 only 2022.
You may have some luck trying older versions but they are no longer supported.

Best regards
Frank

You have to remove all your references to System.Drawing.Common as indicated in the documentation.

The sample code you posted compiles without issues omce you remove the external Datagraph.Ext.Font library which is using System.Drawing.Common (which is based on GDI+ and dropped on Linux by Microsoft). That library is not available on NuGet but my guess is that it’s bringing in the System.Drawing.Common package. You can modify the NuSpec and exclude the asset (see NuSpec documentation).

Hi Frank,

finally, after some experimenting with several test projects, I could pinpoint the cause of the issue to the following:
What I did before the issue came up was, to switch the projects configuration (first the test project and then the “real” one) to enabling Windows Forms and setting the target framework to net8.0-windows; reason for this was that we need to use a reporting library from ComponentOne because the existing code of the application we are porting wo Wisej relies heavily on this library. As the lib is for Windows Forms, this switch was necessary according to their support. (Of course, we only use it for generating PDFs, no WinForms UI 😉  )

Obviously, by this switching of the output type, something got messed up in the .vbproj file; I repeated the steps in a fresh Wisej test application, compared the .vbproj files and adapted accordingly. After this and cleaning up the \bin and \obj folders, the designer works again!

Thanks and best regards, Robert

It seems to be impossible having the correct reference to Font and other System.Drawing object.

You should rename System.Drawing namespace inside System.Drawing.Managed to avoid this behaviour.

hi,

I have reproduced the issue in a small project because the real one is too complex to explain, but the issue is the same.

many thanks,

Luca

Hi Robert,

did you already check our advices in the troubleshooting section here?

https://docs.wisej.com/docs/getting-started-1/troubleshooting#designer-error

Can you please attach your test application so we can take a closer look?

Thanks in advance,
Frank

Hi Mo,

you don’t need a separate license for 4.0. If you’re using a valid 3.5 license you can apply the same key to your 4.0 installation.

Best regards
Frank

I have created a small project but the issue is still there expecially when assigning a property from code behind to the interface.