I ran across what seems to me like an error with the UltraWinComboEdit control. I'm using the Combo in the "Dropdown" mode and I have set the "Nullable" property to False. In my program I'm moving the Value of the Combo to a string and TRIMMING the Value. Like String1 = comboedit.Value.Trim
Unfortunately, if I select an Item from the Dropdown List, then DELETE the Text, then hit Enter WITHOUT Tabbing out of the Combo, to run the screen io processing, it apparently sets the Value to NULL... and consequently causes a Null reference error which, since I set Nullable to False, I don't think it should do that...
Please note;
If I use the Text property in the program instead of the Value, I have no problem.
If I use the Value property with no value entered into the Combo, I have no problem.
If I use the Value property and Tab out of the field after selecting an Item then Deleting the text, I have no problem.
It's ONLY if I select an Item from the dropdown, then Delete it, then hit Enter and move the Combo value to a string WITHOUT tabbing out of the Combo, that I get the error.
Can you fix that?
This does sounds like it might be a bug. What version of the control are you using? Perhaps you just need to get the latest Hot Fix.
Hey Mike, It seems like maybe this issue slipped thru the cracks. I recieved the following email on this, but I can't seem to find the case anywhere... but it could be I just am not looking in the right place too. Could you see if it got lost or point me in the right direction?
Thanx
Case Number: CAS-21446-WC54YOSummary: Possible Error in WinComboEdit control...Last Modified On: April 17, 2009, at 15:51:01 ESTCurrent Contact: Agnew, RandyProduct Release Family: NetAdvantage for .NET 2009 Vol. 1
From: SamSent: April 17, 2009, at 15:51:01 ESTSubject: Value of editor is null when the selected text is deleted after making a selection from the drop down even when Nullable is set to false.
Randy,
I have logged this behavior with our developers in our tracking system, with an issue ID of 16849. This development issue will be assigned to a developer to research for a fix, workaround, or other resolution. If some other resolution is reached, I will contact you with this information.
You can view the status of all development issues connected to this case from the "Development Issues" tab, when viewing this case on the "My Support Requests" page of our website.
Sincerely,Sam
O.K. I've set the Specific Version setting to False and retested it. Same problem.
Hey Mike,
I downloaded and installed the latest hotfix. It didn't change anything as far as this problem goes.
In fact, when I looked at the Reference Properties for UltraWinEditors... the runtime version and version were exactly the same as before. Is there something I have to do to "update" my project to incorporate the hotfixes?
Well, according to the Reference Properties window in VS ...
UltraWinEditors V8.3
Runtime version V2.0.50727
version 8.3.20083.1009
I that what you're looking for?