datagrid | Nette Framework : filtering , sorting , pagination , tree view

I fixed this by wrapping rows and columns in useRefs and used their .current property for both of them. Fixed it immediately.

In the accessibility portion of the documentation, you can find keyboard navigation details for the data grid. Arrow keys are used to navigate between cells and space (among other things) is used to navigate to the next scrollable page. You can find the handling of those keys in the handleCellNavigationKeyDown function in useGridKeyboardNavigation.ts.

When a key down event happens for one of those special navigation characters, MUI calls event.preventDefault() which in your case prevents the key from having its default effect within the input. You can prevent that by using event.stopPropagation() within the TextField onKeyDown such that the event never reaches the grid's keyboard navigation handling code. Keep in mind though that by doing this, you may be harming some of the keyboard accessibility features.

Here's a modified version of your sandbox demonstrating this: https://codesandbox.io/s/cant-add-space-to-muis-textfield-33joy?file=/src/App.js:863-902.

I didn't find a solution for the recursive element, but you can use the columns property on the data-table itself.

Your data-table would look like this

You apparently have a missing await somewhere in your code, which is causing an exception to be wrapped in an AggregateException.

One of the things that await does, as well as setting up the state machinery, is to unwrap AggregateExceptions which hold any exceptions that were thrown during the running of the Task. Therefore, if you want to catch and handle a specific exception type, you should use await all the way down.

so as @Chris Culter mentioned in a comment above, I just restarted my machine and it works again.

It is kind of strange because I already updated my Docker Desktop, restarted, and cleaned/ purged the docker data. None of those helped, just after restarting my windows it works again!

I managed to solve this by doing the following:

I made a property; public static string PreviewedInvoice { get; set; } in the ViewModel of the parent window. In my method that opens the child window (where the preview invoices are to be displayed) I bind it to LicenseHolderID of the rows that have a checked CheckBox, via foreach loop, like such:

Using @adv12's comment, I was able to find this thread. I found this column is called a "row header" using this I could disable it by going Properties > RowHeadersVisible and turning it into False (this.dataGridView1.RowHeadersVisible=false;)

The UpdateLayout call is totally redundant. Modifying the Width will automatically trigger a layout pass. Additionally, both iterations should be merged into a single iteration in order to improve the performance.
The complete implementation is very questionable in terms of user experience: in case the user adjusts the column's width, you would override and reset his customizations, which provides a poor experience. Also the grid would potentially resize itself constantly, which looks and feels odd too. You should at least set DataGrid.CanUserResizeColumns to false.
I believe that adding a column filter, that allows the user to hide particular columns in order to compact the view, has a higher value.

From the code you have posted, it's not possible to tell exactly what is going on or what could cause the issue. The actual layout configuration of your DataGrid control and its context is apparently undisclosed.

However, the issue could be related to how the DataGrid is calculating the width for each column, in case you give the DataGrid a fixed Width and this value would cause the content to exceed the available viewport width (the ScrollViewer would appear in this case):

a) In case of each column width is set to Auto, the DataGrid would simply give each column the required minimum width.

b) In case a column's width is set to star * size, the assigned width is calculated relative to the available remaining space.
In order to calculate a reasonable value, the algorithm would use the effective size of the DataGrid.
The point is, that when using a ScrollViewer, the virtual width would be infinite. Now, if the algorithm would set the last column's width to infinite, you would get a very tiny scroll bar. Therefore, infinite is not a reasonable value. In effect, the final width can not be calculated. That's why the algorithm falls back to use the effective width of the DataGrid, which is the ScrollViewer.ViewportWidth. The result is that all columns must be sqeezed into the available viewport space, causing columns to clip their headers and cell content.

I can provide two solutions.

The first solution is to use a fixed Width for the last column like 1000 DIPs.
This solution does scale very bad. The last column would have either a too small width or a too extreme width that does not make much sense (that's why a reasonable width for the last column can't be calculated - what is reasonable in this context?).

The second and better solution would try to detect if the ScrollViewer can scroll: in this case the last column would be at least partially out of view. This results in a reasonable Width for the last column of Auto: the minimal required space.
The other case, when the ScrollViewer can't scroll, is when all columns are visible in the viewport. This results in a reasonable Width of * in order to allow the last column to fill the remaining space:

It's not mentioned in the doucmentation of XamlReader.Load but any custom assemblies referenced in a XAML namespace mapping must already be available to the application.

You have two options:

1.Load assembly Microsoft.Xaml.Behaviors or initialize some type from the assembly before reading xaml input.