Thank you for the sample. I can reproduce on a IIS only initial startup and a slow connection. It’s a bug in related to this.pictureBox1.SizeMode.SizeMode = AutoSize. Change it to Normal, or any of the other values to resolve the issue. We’ll log the bug.
Here is the link to the project, it’s too big for the attachment. This also happens in the Visual Studio IDE, so it should be easy for you to understand.
The project is too big, i insert a link to the file zip: LINK, I repeat that in the Visual Studio IDE everything is fine, if you publish it on IIS you can see the problem.
Thank you.
Can you give us a code sample? Create a small Wisej project that shows the behavior you are describing and upload it here in a zip file.
Thanks,
Julie
Another thing you can look into- are you using the same theme for the app on the development PC and for the deployment? If you’re using different themes, you might see a difference.
With a Pad height of 35 you can see it, but I don’t think it’s correct behavior.
Regards
The areas you circled are affected by a few different components. You’ll want to use the Theme Builder to edit the JSON directly. Click on the “Editor” tab at the top of the theme builder to see the JSON.
See the picture I attached- I modified the borders to be different colors based on which component they were coming from. I also set the “radius” property to 50 in certain places in order to give it a curved radius.
Panel is in blue, and is a pretty close match to what you want to change.
"panel": {
"states": {
"default": {
"styles": {
"width": 1,
"style": "solid",
"color": "blue",
"radius": "50"
}
},
Resizer is in light green (“#00FF27”,)- it affects the outer border of the area you were looking at
"resizer": {
"states": {
"default": {
"styles": {
"width": 1,
"style": "solid",
"color": "#00FF27",
"radius": "50"
}
}
}
widget is in red, and affects the area you want- but also other areas all over the page.
"widget": {
"states": {
"default": {
"styles": {
"width": 1,
"style": "solid",
"color": "red",
"radius": "50"
}
},
splitter (part of the splitpane) is in yellow, it affects the colors of the lines in the middle
"splitpane": {
"text": "SplitPane",
"states": {
"default": {
}
},
"components": {
"splitter": {
"states": {
"default": {
"properties": {
"width": 9,
"height": 9,
"cursor": "default"
},
"styles": {
"fillColor": "Gray",
"backgroundColor": "Yellow",
"backgroundRepeat": "no-repeat",
"backgroundSize": "20px 20px",
"backgroundPosition": ["center", "center"]
}
},
I’ve also attached a zip file containing the full theme file that I used (Borderradius_differentColors.theme) It’s a modified version of the bootstrap=4 theme. If you want to focus in on the areas I changed, you can do a CTRL+F for the code snippets I shared, or do a textCompare line-by line with the bootstrap-4 theme.
HTH,
Julie
I don’t understand what you asked me, I already sent the two screenshots, can you be more clear?
Thank you very much
Regards
The image is only seen for less than a second and then disappears, then it exists and loads it correctly, at first.
Regards
Hi Francesco,
I think the image is not loading there, would you mind wrapping the sample for us?
Best,
Alaa
Hi Francesco,
Do you have any errors in the console?
Best,
Alaa
Thank you, that fixed my problem.
Shawn R
Hi Shawn,
You’ll need to download the latest VSIX installer from https://wisej.com/builds/ to get the latest Designer.
In late July, Microsoft updated the WebView2 component with Visual Studio and that is what causing the issue you’re having right now.
Best,
Alaa
I have since tried a few other PDF files and the issue seems to have gone. The irony of this is the file was created by the Adobe site for converting word to PDF. I then printed the word document to a PDF printer, and all was good.
Hi Alaa,
Thanks for your answer. However, I think, not sure, that System.Windows.Input is part of .NET, which works across platforms, not only on Windows.
Alex
Hello,
You can achieve the behavior by attaching an Accelerator to the hosting container (Page, Form, etc..) get the focused cell and get or cell its value from there.
Best,
Alaa
Hi Alex,
The new interface is designed to work with Wisej.NET components, changing it to System.Windows.Input would basically mean that it would only be supported on Windows platforms, and Wisej.NET is made to work across all environments!
HTH,
Alaa
Thank you, Julie!
Just wanted to make sure that I didn’t miss anything.
The limitation of the community edition is that it does not include access to premium extensions, such as the DevExtreme library. See here for a comparison of community vs professional edition: https://wisej.com/developer-licenses/
You can see a sample Wisej project using the DevExtreme data grid here: https://wisej-demobrowser.azurewebsites.net/DevExtreme/#dxDataGrid
Source code here: https://github.com/iceteagroup/wisej-demobrowser/blob/main/Wisej.DemoBrowser.Premium/Wisej.Web.Ext.DevExtreme.Demo/Component/dxDataGrid.cs
You mentioned paging specifically- Here’s a code snippet from the example project I linked that sets the pageSize to 10. Note that it is set via the “Options” property of the DataGrid.
this.dxDataGrid1.Options = new
{
paging = new
{
pageSize = 10
},
If you look at this example from the DevExtreme documentation, you will note that the structure of the JSON object is the same as the “Options” property in the Wisej sample. You can always use the component vendor documentation as a guide on how to structure the “Options” property. https://js.devexpress.com/jQuery/Documentation/17_2/Guide/Widgets/DataGrid/Paging/
Additionally, here’s an overview of how the premium extensions, such as DevExtreme, are implemented in Wisej: https://docs.wisej.com/extensions/premium-extensions/overview
HTH,
Julie
