All Answers

Thanks it worked!

Hi Mitch

Have a look in this thread, it might be helpful:

https://wisej.com/support/question/invoke-upload-control-from-a-button

Best,
Alex

Ok, fair enough.   I don’t disagree with your decision.

I had started using the Tag property to store this value.

Mitch

Hi Mitch,

The ListViewColumnType is a VWG addition, it’s not present in WinForms. We used WinForm as the base class model while removing all items that would be obsolete on a web platform (like 3D borders) and adding a lot of additional web-css3-html5 features. While our main goal (and necessity) was to replace VWG we also didn’t want to replicate features that have probably been added over the years to cover various shortcomings (at least not from the start).

The ListViewColumnType is a strange property since it doesn’t specify just the data type (it has Icon and Control), it’s only used to render the cells, and the only value type that can be stored in ListViewItem is a always a string anyway – unlike the DGV which supports any type. It looks like VWG tried to use the LV as a DGV with mixed results. The enumeration is a mix of data type and visual widget type (limited to Icon and Control).

You can add a Type property (or any other property) to ColumnHeader or ListViewItem in two ways:

• Extend ColumnHeader -> MyColumnHeader : ColumnHeder. The editor will automatically detect any subclass and will show you the list of subclasses at design time.
• Or use the UserData property (all Wisej components have it and it’s a lot better that the Tag object) like this: this.columnHeader1.UserData.valueType = typeof(int), or like this this.columnHeader1.UserData[“valueType”] = typeof(int). The UserData property is a dynamic object that can store anything with any key.

Best,

Luca

Thanks.. Perfect.

We are going to support child rows. It’s kind of already there since it’s needed for the PropertyGrid, but it’s not available in the DataGrid by itself yet.

See attached image of the PropertyGrid preview internally using the DataGrid with child rows.

We also already support ColSpan and RowSpan, see the cell style property.

/Luca

Hi Mitch,

You can use the MessageBox (or any other modal dialog) in several ways: blocking modal and non-blocking modal, with callback and any combination. The blocking modal is the most common and simpler since the code stops waiting for the result:

Blocking Modal

var result = MessageBox.Show("Yes or Now?");

// code here is executed after the message box is closed.

Non-Blocking Modal

MessageBox.Show("Yes or Now?", modal:false);

// code here is executed right away.

Blocking Modal with callback

var result = MessageBox.Show("Yes or Now?", (r) => { 

// code here is execute when the box is closed, r = DialogResult.

});

// code here is executed after the message box is closed.

Non-Blocking Modal with Callback

MessageBox.Show("Yes or Now?", modal:false, onclose: this.MessageBox_OnClose);

// code here is executed right away.

private void MessageBox_OnClose(DialogResult result) {

   // code here is executed after the message box is closed.

};

HTH

Best,

Luca

Hi Thomas,

The WebBrowser control is not implemented yet. Use the IFramePanel for now, it’s basically the same.

Best,

Luca

That is Visual Studio asking you if you want to enable the debug property in Web.config. It should ask only once though, unless you switch to Release.

It’s almost complete. The control is already available (not in the toolbox) and it’s read-only. It should be completed by the end of this month.

Hi Mitch,

I have added an enhancement to add a property ListViewItem.RowHeight. Currently you can set the row height of individual rows only with the DataGridView control. But since the ListView control in Details view uses the DataGridView widget it should be no problem to add the RowHeight property.

You can also change the default row height for the ListView in the theme.

We also still have to complete the auto resizing implementation.

Best,

Luca

Hi Alex,

The fix was related to the Up/Down keyboard arrows (it also added PageUp and PageDown support) and broke the Up/Down button arrows. It is fixed and included in the current build which should be released tomorrow, also the Up/Down buttons are now repeat buttons – keeping them pressed repeats the click. Currently there is the development build 1.3.20 available for downloading (it still has this problem though).

Thanks!

/Luca

Hi,

Unfortunately, the fix in 1.3.18, which I just checked, was rather radical ! I mean, the wrong behaviour I described is not there any more, but now the up/down arrows do nothing! Clicking on them does not affect the control value at all. You can check it with the original attached test project.

Best,
Alex

Thanks.. will look for the new release, or if you have it on a dev build to download.

Unfortunately it’s a bad regression, related to the recent datagrid rendering improvements. It’s fixed in dev, should be available soon.

Thanks!

Tanks again for the swift support!!

Hi Michael,

It’s a regression at design time introduced with the new property AutoHideTaskbar when set to true. It’s fixed in the current dev build (coming up). If you set AutoHideTaskbar = false (or remove the line AutoHideTaskbar = true) from designer.cs in InitializeComponent() you can open the desktop in design mode.

Best,

Luca

Hi Luca,

This thread is really important for us at HRTMS.

Do you have any idea on the time frame for a mobile offering?  We are looking at Angular 2.0 as an alternative, but really like the productivity of your tool.

Its a such a difficult decision since we are unsure of your timeline.

Thanks in advance,

Mitch Stephens

Thank you for the test case. I will let you know what we find.