We have recently renewed our licence, in order to upgrade our solution to version 2 of the framework and take advantage of impersonation capabilities that are not included in version1. In preparation for the upgrade,which is also entailing us upgrading our .Net Framework version, I have been doing an offline dry run with the new version. I have upgraded everything according to the resources I found with regards to the upgrade steps. I have managed to resolve several issues that have cropped up, whereby logic that worked in version1 now no longer works.
Please note that your upgrade instructions that I found at the following resource did not include a step to also replace any version 1 extention references with the new version extention dll’s. You may want to amend that, as it did cause me a headache:
The following is what I picked up with version 2:
Version1: MessageBox.Show(“mymessage”, “mycaption”, MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1, true, keepOnScreen, rightToLeft, onClose);
Version2: MessageBox.Show(“mymessage”, “mycaption”, MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1, AllowHTML, true, keepOnScreen, rightToLeft, onClose);
Public Sub LoadCombo(Combo As ComboBox)
Public Sub LoadCombo(Combo As Wisej.Web.ComboBox)
but had to be changed to:
Public Sub LoadCombo(Combo As ComboBox)
Public Sub LoadComboWiseJ(Combo As Wisej.Web.ComboBox)
In the attached screenshot, I placed the cursor between the ‘b’ and ‘c’ in the existing text of ‘abcde’ and entered a ‘4’. The text updates correctly, but the whole text is selected, even though my logic is requesting that the cursor be placed after the last typed character(in this case the ‘4’)
Please can you review the attached test case and address the last 3 items above, concerning the IsVisible property and the UserComboBox? It is critical that they be resolved one way or another, as we are very close to going live with the WiseJ version of our System.
All the above seems like quite alot of issues to have to experience with an upgrade. My superiors would like to know if there is any indication whether this is more a once -off occurrence with the move from ver1 to ver2, or is it likely to experience issues every time an upgrade is done(for example upgrading to version3 next year with .Net Core support)?
I have attached the Designer and Code file for a simple form with a UserCombBox and panel (Please see Window1.zip)
I tried your code after fixing some issues and also tried a new test:
private void userComboBox1_DropDown(object sender, EventArgs e)
this.userComboBox1.DropDownHeight = 200;
I can set the DrownDownHeight before or after it’s dropped down and it always works.
About the ComboBox performance, the issue was the browser not being able to handle too many elements. Several builds ago we added the VirtualScroll property to the ComboBox, ListBox, and TreeView allowing the to handle unlimited items without any performance loss.
Hi Luca and Frank. Thank you for fixing the Caret/Cursor issue. I see it is working now with the latest version whereby I just need to set the new SelectionStart and SelectionLength.
I haven’t seen any further mention of the other issue, also with regards to the UserComboBox, whereby setting the DropDown height and Width in the DroppedDown event no longer has an effect, and the change is only applied the next time the DropDown is shown. I have tested with the new version and the issue persists.
‘The UserComboBox DropDown event can no longer set the height of the DropDownControl. This worked in version 1 of WiseJ. The height gets set without errors, but only applies the next time the Dropdown is shown(ie the next time the user opens the DropDown, the previous height is then applied). I have tried using an Application.Update but it has not effect. Please see event userComboBox1_DropDown in the attached test case form. I have included a screenshot (UserComboBox issues.PNG) showing the dropdown height unchanged after setting it in the event. It should have changed to 200.With a Custom ComboBox I wrote ages ago, using a UserComboBox and Datagridview(which our system is very dependent on), I have overcome this issue by doing the dropdowncontrol height setting in other places like the logic where comboBox list items are added or removed. This will most likely result in a performance hit, which is precisely the very reason I wrote a Custom control (ie. the standard WiseJ ComboBox in version 1 experienced a serious memory bloat issue with large lists). I am yet to stress test my fix.’
The attachment is not runnable, but I copied it into another project to try and also looked at the code:
Hi Luca. Thank you for the response.
‘I have attached the Designer and Code file for a simple form with a UserCombBox and panel (Please see Window1.zip)’
The separator has been renamed to Spacer, as documented.
The allowHtml is an optional argument that should be used by name (I’m not familiar with VB.NET but in C# you use allowHtml:true) regardless of the position. The default arguments have remained unchanged.
Autosizing or rows and columns was not implemented at all in 1.5 so the enumeration value that has been removed didn’t have any effect.
The overload issues that you reported are not related to Wisej, since it’s not a compiler.
The IsVisible property was misleading and was meant to be used internally since it was returning the internal raw VisibleInternal value. The Visible property returns whether the control or its parent are Visible. If a control has Visible = true but the parent has Visible = false when checking Visible on the control it returns false.
About the UserComboBox issue, please send a sample that we can run and I’ll be happy go over the specific issues. In the mean time I’ll try to reproduce.
Please login first to submit.