+1
Corrigé

When I use the search function, Wieldy 0.2.6.656 often crashes

Anonyme il y a 14 ans mis à jour par Kevin Erath il y a 14 ans 1
"Ein unerwarteter Fehler ist aufgetreten".

System.Reflection.TargetInvocationException: Ein Aufrufziel hat einen Ausnahmefehler verursacht. ---> System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei Wieldy.Client.Modes.Todo.ActionListControl.RefreshActions()
   bei Wieldy.Addins.Sdk.NotifyEventHandler.Invoke()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   bei System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   bei System.Delegate.DynamicInvokeImpl(Object[] args)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

Solution

Solution
Corrigé
fixed with beta V0.2.6.658
I have analyzed this a bit more and found it was actually my fault. I have written a small script to convert tasks from TimeGT to Wieldy, adding them to the Local.dat file. However, for actions with no additional notes, I did not create an empty "Notes" tag, but just omitted the tag. This does not seem to be a problem for Wieldy, everything works fine for these actions, but it crashes if these actions without Notes tag are found in a search. Maybe you can make it a little bit more robust in this regard.
Solution
Corrigé
fixed with beta V0.2.6.658