All Answers

Hi,

I have added the postback processing, private void ejSpreadsheet1_WebRequest(object sender, WebRequestEventArgs e) so it is not reasson for error.

I was using syncfusion.ej from nuget (which then downloaded a whole lot of other packages as dependencies), now I found in wisej.web.ext.syncfusion.test there is a Libs folder, when I added reference to there libraries postback is working ok

The sorting also is not a bug. The only value in the cell is the key when the combo box has a ValueMember and a DisplayMember. The display value can change at any time. In fact winforms (attached) sorts the same way. And it’s also the same way the database would sort it since the display value is just a lookup. You can implement or change the sorting by attaching to DataGridView.SortCompare or by using Sort(IComparer).

HTH

Looks like what you did works correctly. You added it to the ChartJS.Packages. What is the issue?

Hi Frank

Thanks how do you explain the image I uploaded earlier showing that the column header height had increased when the grid contained rows, but not the height of the blank header column above the row header? I can’t understand why this is happening.

Is the gdi scaling out of sync with that required by the control?

How would I use the theme to fix this

Thanks for your help

Ewan

Hi Dino,

I tried the original sample that simply shows the postback url. It is correct. The reason is that what you want to do with the callback has to be decided by your app. Look at the Component/ejSpreadsheet in Github. You have to attach to WebRequest and then decide what to do with the data. Which also answers your last question since the data is available on the server.

This is in the example.

 private void ejSpreadsheet1_WebRequest(object sender, WebRequestEventArgs e)
 {
 // load the file?
   if (e.Request.Files.Count == 1) {
     e.Response.Write(LoadFile(e.Request.Files[0].InputStream));
   }
   else
   {
     SaveFile(
       e.Request.Form["fileName"],
       e.Request["format"],
       e.Request["sheetModel"],
       e.Request["sheetData"]);
   }
  }

 private void SaveFile(string fileName, string fileFormat, string sheetModel, string sheetData)
 {
   switch (fileFormat)
   {
     case "xls":
      Spreadsheet.Save(sheetModel, sheetData, fileName, ExportFormat.XLS);
      break;
    case "xlsx":
      Spreadsheet.Save(sheetModel, sheetData, fileName, ExportFormat.XLSX);
      break;
    case "pdf":
      Spreadsheet.Save(sheetModel, sheetData, fileName, ExportFormat.PDF);
      break;
    case "csv":
      Spreadsheet.Save(sheetModel, sheetData, fileName, ExportFormat.CSV);
      break;
   }
 }

Refer to the Syncfusion docs for the Spreadsheet API.

HTH

Hi Luca.

Thanks for the explanation. I was on the right path, I guess, but I went from the Form object straight to the Button, and skipped the Panel, GroupBox, etc.

On the Uploader Theme, it means then that there is no way to apply an Appearance key directly to the Button, right? I thought it would be possible reading one of your answers on the forum ( https://wisej.com/support/question/upload-files-not-working-on-firefox ). Sorry if I am making a confusing out of it. 🙂

Hi Ewan,

AllowSortingDatasource = false allows you to implement your own sorting if the data source doesn’t support it and you don’t want wisej to sort it for you. Showing the sort order is correct. It’s the same as SortMode.Programmatic. The sort glyph is displayed, the SortedColumn and SortOrder properties are updated, but the actual sorting is up to the program. Otherwise set it to NotSortable.

The original error you report has been fixed. It’s in the latest dev build but it turns out the dev build has other issues unrelated to this so I’d wait for the release build.

The sort glyphs as all icons in wisej scale with the browser and gdi scaling, not the control. To scale the icon you can use the theme. Otherwise a tall column header would have an impossibly scaled icon. All grids I have tried do the same

> If I sort a combo box column the key is sorted not the display data.

That’s a bug. Thanks!

The object model is the same as in your app using the names of the controls. The main page is App.MainPage. The desktop is App.Desktop, each floating window is App.[window name]. If there are multiple with the same name it’s an array. I.e. App.frm1.panel1.groupbox1.textbox1.

You can pass controls to javascript as parameters and Wisej will marshal it back and forth. I.e. this.Call(“doSomethingWithButton”, this.button1); will call doSomethingWithButton(button) on the client where “button” is the client widget that corresponds to the server control.

You can also get an object by id using the Control.Handle. That is the unique id of the control also on the client (with the “id_” prefix).

The Upload control is not a button, it’s a composite widget with a textfield and a button and a container. See below. The native upload <input> cannot be styled.

After inserting the row at the top the current cell is still the current cell which is always the last row since you insert above. The current cell will scroll into view, which is correct.

Looks like you have set AutoSize to true to make the datagarid grow vertically hence it will never show the scrollbars. To scroll the parent set AutoScroll to true on the container.

Hi Nello,

Thanks for the information!

DGV.ScrollRowIntoView() not working is a bug, I’ve logged it as issue #2543. We’ll try to get a fix for the next build. In the meantime… you should be able to use ScrollCellIntoView, I tested it and it seems to be working. Please let me know if you have issues with it.

When using DGV.Rows.Add and DGV.Rows.Insert, WinForms does not scroll to the bottom of the DGV. I will see if we can change this behavior in Wisej or if we should log an enhancement for an optional parameter (i.e. shouldScrollToBottom). Either way, fixing ScrollRowIntoView should solve your issue.

I’ll keep you updated!

Best,

Levie

Hi Levi,

thank you very much for response!

ScrollBars property set to Both

I am using a DataSource

I am using Firefox, Edge has the same result.

I am using the latest Update from today 2021-01-28

I already looked to another Project and it is working with both scrollbars but i can’t figure out the differences.

Hi Theo,

I need to collect a bit more information from you to diagnose the issue.

• Did you set the ScrollBars property to Both?
• How are you populating the DGV (setting a DataSource, using this.DGV.Rows.Add, etc)?
• Did you try with a blank project and compare the properties of the DGV?
• What browser are you using?
• What version of Wisej are you using?

Let me know!

Best,

Levie

Hi Luca.

I now used your second advice and it worked perfectly. Nevertheless, if you could give me some tips on how to properly find out the Object Model full path to be able to use the Client Event as you described, it would be great.

By the way, the main reason I am going through all this is because I wanted the Uploader to show its button with the same Theme as the other buttons in the form. Changing its AppearanceKey showed it properly at Design Time, but once I run the application, the button shows all messed up.

Cheers.

Ivan

Hi Frank

Using 2.2.33 I notice the following:

1. if set AllowSortingDatasource to False the sort arrows still appear which is misleading to the end user
2.  if set AllowSortingDatasource to True the error has gone for an empty dataset – fixed
3. If I click on the header row the appearance of the sorting arrow causes the height of header to increase but not the row header header height (when there is data in the grid)
4. If I sort a combo box column the key is sorted not the display data.

I have set the column header height to 25 and would have expected the sort arrows to scale.

Thanks for you help

Ewan

WebSocket is irrelevant since wisej will reconnect it automatically or work with http. Anything with the token authorization is in cookies than you can check if they already exist. I doubt you can force a new token without re-authorizing.

If default.html loaded then it’s authorized which  means that the request to resource.wx must work or it’s a wrong installation. Basic IIS authentication should be configured for the entry page, which can be an html or an aspx or php or anything else.

Hi Simone,

issue #2526 is fixed in our latest Wisej development build (2.2.33).

Best regards
Frank

Hi Glenn,

the fix is available in Wisej development build 2.2.33.

Best regards
Frank