Hello,
I have experienced a problem with the XamComboEditor: When I set start typing in the XamComboEditor in order to get the search results I receive a crash:
bei Infragistics.Controls.Editors.ComboEditorBase`2.ChangeType(Object value, Type dataType) 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 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) bei System.Windows.Threading.DispatcherOperation.InvokeImpl() bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state) bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj) bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) bei MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state) bei System.Windows.Threading.DispatcherOperation.Invoke() bei System.Windows.Threading.Dispatcher.ProcessQueue() bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) bei MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) bei System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) bei System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame) bei System.Windows.Application.RunDispatcher(Object ignore) bei System.Windows.Application.RunInternal(Window window) bei System.Windows.Application.Run(Window window) bei System.Windows.Application.Run() bei AppFact.Shell.LOB.App.Main() in D:\Software Development\Bauradar Experimental\Bauradar.Shell\obj\Debug\App.g.cs:Zeile 52.
If I remove one property by another to see how it gets stable I stop with this working version:
<ig:XamComboEditor AllowMultipleSelection="True" ItemsSource="{Binding Bau2Org}" DisplayMemberPath="Organisationseinheit" CustomValueEnteredAction="Ignore" Grid.Column="1" Grid.Row="5" Style="{Binding Source={StaticResource ControlBaseStyle}}" TabIndex="104" AutoComplete="False"> </ig:XamComboEditor>
Unfortunatly the most needed functionalty (Checkboxes and Search) are gone then. This is the crashing version:
<ig:XamComboEditor AllowMultipleSelection="True" ItemsSource="{Binding Bau2Org}" DisplayMemberPath="Organisationseinheit" CustomValueEnteredAction="Ignore" Grid.Column="3" Grid.Row="5" Style="{Binding Source={StaticResource ControlBaseStyle}}" TabIndex="105" AutoComplete="True" AutoCompleteDelay="50" IsSelectedMemberPath="IsSelected" CheckBoxVisibility="Visible"> <ig:XamComboEditor.ItemFilters> <ig:ComboItemFilter FieldName="AnzeigeFeld" LogicalOperator="And"> <ig:ComboItemFilter.Conditions> <ig:ComparisonCondition Operator="Contains" /> </ig:ComboItemFilter.Conditions> </ig:ComboItemFilter> </ig:XamComboEditor.ItemFilters> </ig:XamComboEditor>
Please advice how this can be stablized.
I am not sure if this issues is related to https://www.infragistics.com/community/forums/t/110430.aspx . If it is I would like to understand in with version/service pack its fixed.
Thanks
Niko
Hello Niko,
I can confirm that the issues that are mentioned at the forum thread you referenced (https://www.infragistics.com/community/forums/t/110430.aspx) are fixed internally, and are currently awaiting release. They should be included in the next service release estimated to come out on October 13.
I am not entirely sure if these issues are really related to the crash that you are seeing, though, as there is no mention of a crash on that referenced forum thread. In an attempt to reproduce this behavior you are seeing, I have put together a sample project with the pieces of the XamComboEditor that you have provided - with the exception of the Style that you are using, as I am not entirely sure what your "ControlBaseStyle" is referencing. In doing so, I was unable to reproduce any sort of exception in this case. I am curious, though, as to what type of exception you are actually seeing (e.g. NullReferenceException, InvalidOperationException, etc.)?
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 16.2.20162.2109 in Infragistics for WPF 2016 Volume 2.
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 you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate Developer
Hello Andrew,
I have adapted the sample project and copied the original XamComboBox into the XAML.
It turned out that the ComboItemFilter FieldName "AnzeigeFeld" simply does not exists. If I try the same FieldName in the sample project I receive an error already at startup during the parsing of the XAML.
The issues is resolved.
Thanks a lot.
Thank you for your update on this matter. I have reproduced the behavior that the XamComboEditor crashes when typing when the "FieldName" of the ComboItemFilter doesn't exist. This is expected, as the XamComboEditor does not know what to filter on at that point, and so it crashes.