Hi,
I have an application with a grid with several info and i want the users can hide or order the columns and save the appearance of the grid.
I'm using the save method of the displaylayout to achieve this but the saved file size is about 100 MB ( several times it dont save the file and throws an OutOfMemoryException).
I dont knok if i'm using correctly this method or if its somethig i'm missing (¿Is there any PropertyCategories that save the order, hide state and group by state of the columns?
I'm using the 8.2 version of infagistics.
Thanks.
Hello,
This seems to be an issue which has already been fixed. So what you could do is to download the latest service release available for your current version or either download the trial version of Net Advantage 11.2 and test your application against it.
Thanks for your answer.
I've tryed to upgrade the version whith the upgrade utility but the application stops working (i think its somethin in the initializeComponent event) and i cant open the form designer either.
Thanks for your answer Mike!
I've finally achieved to upgrade the application to the Infragistics 12.1
The only thing i've noticed so far is a problem with some controls such ultratexteditors and ultradatetimeeditors. In design time i create a ultratexteditor and its heigth property is ser to 21 bydefault but when i execute the application it is shown with heith 24. When i executed the application "step by step" i saw that after the line "this.txtCodigo.Size = new System.Drawing.Size(197, 21);" is executed, the value of this.txtCodigo.Size is (197,24) however When i change the property AutoSize to false it change right the property size.
Are you loading an application style library file into your application? If so, then the isl file could be changing the font and thus the control is getting bigger at run-time to accommodate the larger font size.
It's also possible that you the height is increasing because you are displaying an editor button on the control.
Thanks again for your answer Mike,
There was an style library file with the "Segoe UI". When i changed the font it worked fine.
Now i have another problem with all the UltraCombo. The combos are binded to lists of elements (for example an EClient) and the combo has the AutoCompleteMode to SuggestAppend. When i write something that is not in the list of EClient the application throws an exception of trying to convert a String to an EClient. I think the previous version of Infragistics we had throws this exception when you leave the control, not while you are writting.
Is there any property of the UltraCombo that is making this behaviour?
I'm pretty sure the Exception you are seeing is a FirstChance exception. It's getting caught and handled by the grid, so you will only see this if you have set the IDE to break on all run-time exceptions.
When you type something into the combo that is not on the list, the Combo will return the string you typed as it's Value - since it cannot convert it to an object. There's no way around that.
I'm not aware of any reason why this should have changed - it has always done this. But if the behavior did change, then we could look into it and see if we can determine why. Can you reproduce the exception in a small sample project and post it here so we can take a look?
I was wrong about the cause of the exception.
We are trying to cast the value of the combo to an EClient on the onValidate event. (EClient myClient=myCombo.Value)
Before the update the value of a element that doesn't exist in the list of the combo was null but if you write swf in the combo, the value of this combo is swf instead of null. When we try to cast "swf" to EClient throws the exception.
Is there any property of the combo we could get the value of a non existing element as null instead of the text?
The intended behavior of the combo is that when you type something into the edit window that cannot be matched to something on the list, the combo returns the string you typed as it's Value.
There was a bug introduced a few years back where the control was returning null, instead. This bug was then fixed. So the current behavior is correct and there is no way to change it.
But this should be very easy for you to handle. All you have to do is check to see if the combo.Value is EClient and if not, use null.