Hi Alex,
2) is by design, send you a mail with further information
3) is a bug, logged as WJ-7635
Best regards
Frank
One more thing. You can also use the Wisej designer with wijmo widgets but there is an issue where wijmo doesn’t like dom ids starting with a number, we’ll fix that in Wisej. And your code has a getCountries() child method declared after it’s used; it’s fine in Chrome but generates a SyntaxError in IE. It should be declared before it’s usage.
You can also decide what to use at design time in your initialization script testing wisej.web.DesignMode. And… Somehow wijmo took over the dom and has slapped a trial notice on all widgets, including ours. See image below.
Hi Luca, Frank
Sorry. Didn’t change my code from CurrentCell to CurrentRow. It’s now working.
Thanks.
As a workaround until the next update, you can change <compilation debug=”true”> to “false”. The extra character is the BOM added by a .NET stream used only when in debug mode.
Forgot to add that now the DGV can only select rows. The SelectionChanged event fires when the selected rows, and later when supported the selected cells and columns, change.
When the current cell changes it fires CurrentCellChanged. The sequence is:
HTH
Best,
Luca
CurrentCell is null when clicking on the row header – do you also get CurrentRow null?
Luca,
thank you for superfast support.
There is only one example, I plan to make the other third part controls of wijmo available in Wisej.
Regards,
Alexander
Hi Frank,
Sorry but I am getting the same error. Please see attached image.
I forgot to mention that pressing left and right arrow keys or mouse-click to navigate to cells on the same row doesn’t fire the SelectionChanged event. It fires with up and down arrow keys of mouse-click on a different row.
Build 1.2.66.0.
Thanks.
Thanks. There is an extra \ufeff character in the concatenation of the css. I don’t know where it’s coming from, could be an end of stream. It will be fixed in the next update. It works as soon as I delete it by hand. See image below. You can also easily modify the themes to have the same look as the wijmo combobox, if that’s what you need.
Best,
Luca
Hi Luca,
thanks for fast response . Yes, it’s working now, the styles are loaded.
Well I have another problem now . Not all styles are applied for third part control.
I have created two small examples (s. attachment): a simple web application and Wisej application. In both I create third part javascript control wijmo.input.ComboBox. The style wt-content is not applied for my combo in Wisej application.
Best Regards,
Alexander
Thank you, Frank, NodeFont works nicely now.
What about the other two? I didn’t understand whether you are planning to do something or they are by design.
Best,
Alex
Hi Cris,
WJ-7629 is fixed in the latest build (1.2.66).
Best regards
Frank
Hi Alex,
1) logged as WJ-7632, fixed in the latest build (1.2.66)
Best regards
Frank
A new build (1.2.66) has been uploaded.
Themes
Includes a minor update to Material-3 and the Classic-2 theme is now built-in.
Fixes
| Item | Type | Priority | Severity | Title | Resolution |
| WJ-7629 | Bug | Medium | Major | DGV.SelectedRow is null when there is no current cell and a row is selected. | Complete |
| WJ-7632 | Bug | Low | Trivial | TreeNode.NodeFont doesn’t update the font of the node. | Complete |
| WJ-7628 | Regression | Medium | Minor | The DateTimePicker grabs the focus when updating the value. | Complete |
| WJ-7630 | Bug | Medium | Minor | A new DGV is initialized with CurrentCellAddress(-1,-1) – it should have the first visible cell as the current cell. |
Complete |
Hi Luca,
Got you. And I understand that your target first release date is fast approaching. What I asked maybe just considered as an enhancement and can be done after the first release if you are running out of time.
Just please include that in your TDL.
Thanks.
It is possible, but not yet 🙂
The DGV cells in Wisej have the Control property which is meant to be used to include a control in the cell, any cell. The top left cell is DGV.TopLeftHeaderCell, so you can assign a control to the call, the control can be created dynamically and all the events are wired back normally.
However the property is not wired on the client side yet and I’m not sure it will be by the first release.
Best,
Luca
Hi Luca,
Exactly. So that if I test SelectedRows before deleting a row, the test always fails. An option is to click any cell in the same row to delete which doesn’t make sense to me.
Thanks.
Hi Cris,
The behavior of the DGV when clicking on the row header is slightly different than WinForms. Wisej supports clearing the current cell while WinForms always selects the first visible cell unless cleared by code setting it to -1. In this case the bug is that SelectedRow also returns null while it should be the current row.
It’s WJ-7629.
Best,
Luca
Add it to the project under \Resources or \Platform as an embedded resource. Then in AssemblyInfo.cs add
using Wisej.Core; [assembly: WisejResources()]
The WisejResources attribute makes the Wisej engine take the js and css embedded files, bundle them (and minify if debug=false in Web.config) and serve them back to the client as two single bundled files: wisej.css and wisej.js. You can also copy in the wijmo js instead of linking the source in packages. The files are bundles in alphabetical order.
Best,
Luca
I don’t have an ETA. It’s almost all there but, unsurprisingly, time is running faster as we approach Nov 1st. Best guess is before the end of the year in the extensions (with source) and probably not covering 100% of the features in the javascript widget.