Hi
I'm binding a virtualized collection (from the site: http://www.codeproject.com/Articles/34405/WPF-Data-Virtualization) to the XamComboEditor. However I'm getting an error, the stacktrace:
bei System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate) bei Infragistics.Controls.Editors.ComboEditorBase`2.SearchAndFilterItemsByText(String text, Boolean performAutoComplete) bei Infragistics.Controls.Editors.ComboEditorBase`2.ProcessEditorText(Boolean allowDropDown, Boolean attemptAutoComplete) bei Infragistics.Controls.Editors.ComboEditorBase`2.DelayTracker_Tick(Object sender, EventArgs e) bei System.Windows.Threading.DispatcherTimer.FireTick(Object unused) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) bei MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) bei System.Windows.Threading.DispatcherOperation.InvokeImpl() bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
I can see that it tries to take the first element which I assume this happens before the list is filled using data virtualization technique. Is there a way to override this combo editor process?
Hello Marco,
I followed the steps you suggested and was unable to reproduce the behavior you're describing. I modified the project given on the site http://www.codeproject.com/Articles/34405/WPF-Data-Virtualization to use a XamComboEditor and was unable to reproduce the error you are experiencing.
I have attached the sample project I used to test this. Please test this project on your PC; whether or not it works correctly may help indicate the nature of this problem.
If the project does not work correctly, this indicates either a problem possibly specific to your environment, or a difference in the DLL versions we are using. My test was performed using version 14.1.20141.2027 in Infragistics for WPF 2014 Volume 1.
If the project does show the product feature working correctly, this indicates a possible problem in the code of your application. It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing.
Or, if this sample project is not an accurate demonstration of what you're trying to do, please feel free to modify it and send it back, or send a small sample project of your own if you have one.
Please let me know if I can provide any further assistance.
Sincerely,AndrewDeveloper Support IInfragistics Inc.www.infragistics.com/support
Hi Andrew
The problem occurs when the SelectedValue is also set. When you start typing the first key gets the data and the 2nd key generates an error. (see attached file)
Just a background info, I'm building a form eg. where the user could set the customer (id is bound to Order.CustomerID) for an order. The field for the customer is a XamComboEditor in which the user would type and gets a list of filtered items. The XamComboEditor has predefined ComboItemFilters set. And there are around 40k customers in the database.
Development Issue 173723 has been resolved and fixed in the latest service releases for 2014.1. The service release is now available under your account at the Infragistics Website.
Please let me know if this service release resolves the issue you were having with the XamComboEditor with virtual collection.
I have investigated your issue, and I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 173723. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.
I have made this case viewable to you. It has a case ID of CAS-138374-V9D0V1. I will update you with any new information after the review. You can also continue to send updates to this case at any time.
Please let me know if you need more information.
I have downloaded your sample and I can reproduce this error. I tried to find a workaround for it, to no avail.
I believe this may be a development issue, so I have passed this issue on to our Development team and I am awaiting a response from them. When they update me, I will update you.
Please let me know if you have any questions or concerns.