All Answers

Hi Nicholas,

I have attached an updated sample, please let me know if it works for you!

Best regards,
Alaa

//

You say “the difference appears after conversion”, so I presume if you have a Winforms version and a Wisej version of the same project, it has the scaling issues in the Wisej version?

Try looking into responsive profiles:
https://wisej.com/tools/responsive-properties/
https://docs.wisej.com/mobile/guides/responsive-design

Marhaba Fahad,

In addition to what my colleague Julie suggested, you’ll have to know that the migration process would require a bit of manual adjustment to get the layout you desire, and that is due to the theme and fonts used by the application.

If you want a mobile friendly interface, you’d want to adjust the layout accordingly using the responsive properties as mentioned above, we do offer services for designing a UI if that suits your needs, for more info please use this contact form: https://wisej.com/ui-design-request/

Make sure that you add the view-port meta tag to your HTML file as well.

Best regards,
Alaa

Hi Nicky,

Please go to https://docs.wisej.com/deployment for more information on how to deploy a Wisej.NET Application on Linux.

Best,
Alaa

//

This is a video on how to deploy a Wisej project on Linux https://docs.wisej.com/deployment/targets/linux-macos

Thank you, Alaa. The example was more than wonderful. I developed it so that it exports the PDF file to the C disk without displaying it directly, while linking it to the MYSQL database. I have attached the example for benefit.

Download the modified example

https://www.mediafire.com/file/xhzvsoss9bco0qr/WisejNET.CrystalReports.VB.rar/file

Hi,

Enclosed is a link to a testproject.

https://drive.google.com/file/d/11304927n1QArCunIsOHRGiNkaZjwhhhV/view?usp=sharing

Hi Fahad,

in Wisej.NET applications that we created we usually export Crystal Report results to PDF and use the PDFViewer component to display them.

Best regards
Frank

Hi Per,

can you please wrap up a test case that clearly shows the issues you are facing i.e. the events that are not fired?

Thanks in advance,
Frank

Hi Asen,

all project types are explained in our documentation.

Best regards
Frank

Hello Julie.

Thank you for your answer, I put the css line into the theme file that I use but only have partial success with it. When I have a datagridview with no data and no column headers I can see the nice rounded corners on all 4 corners, looks good !. But when I have a row of data in the datagridview the row does not have rounded corners and, on screen, overwrites the datagridview border and gives it square corners. Likewise if I have column headers – the column header row has square corners and you can’t see the rounded corners of the datagridview anymore. I have attached an image which might make things clearer.

Andrew

You can do this via a theme/ theme mixin.

This is the code you need:
"css": "{\"border-radius\":\"5px\"}"

You need to use this in the “table” like so:
"table": {
"states": {
"default": {
"styles": {
"width": [1, 1, 1, 1],
"style": ["solid", "solid", "solid", "solid"],
"color": "windowFrame",
"css": "{\"border-radius\":\"5px\"}"
},
"properties": {
"indent": 20,
"rowHeight": 32,
"headerCellHeight": 32,
"backgroundColor": "window",
"headerBackColor": "window"
}
},

I’ve attached the full theme file (it’s a modified version of the Bootstrap=4 theme) and a screenshot of what this looks like on the datagridview in the theme builder.

Hope this helps,
Julie

Hi Tim,

accessing the single values is as easy as this

var Settings = Application.Configuration.Settings;
var CallBackPath = Settings.AzureAd.CallbackPath;
var Scopes = Settings.DownstreamApi.Scopes;

AlertBox.Show("CallBackPath=" + CallBackPath + " Scopes=" + Scopes);

Best regards
Frank

I had a similar issue, when the designer started to forcefully insert AutoGenerateColumns = true into all the DGVs.

The reason seemed to be that I had this property in my DataGridViewExt middle-class.

        [DefaultValue(false)]
[Browsable(true)]
public new bool AutoGenerateColumns {
set => base.AutoGenerateColumns = value;
get => base.AutoGenerateColumns;
}

All I needed is to remove this overload from the middle-class, and the designer seems to be OK now.

Hi Tim,

it worked for me okay using your default.json and just changing the startup parameter.
Find sample attached.

Regards
Frank