This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi There, We have an application that uses a work thread to do the calculation, when some more data is ready to show, we will let the main thread know so that main thread can get the data and update the graph. But some times, it will throw the exceptions and crashes. We did exactly the same thing on using Version 5.0 and it is fine. We are using April 19, 2014's nightly build Version 6.0 and the following are exceptions: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.OverflowException: Negating the minimum value of a twos complement number is invalid. at System.Math.Abs(Int32 value) at Mindscape.WpfElements.Charting.ChartAxis.#Asc() at Mindscape.WpfElements.Charting.ChartAxis.#wsc(Boolean raiseEvent) --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) Gordon |
|
|
|
|
Hello Gordon Thanks for pointing this out. I have not reproduced this, but it looks like this may have been introduced when I improved the auto-label-step calculation. I found an potential unchecked divide by zero issue which would have caused NaN to be passed into a Math.Abs call thus caused the error. This has been fixed up for the next nightly build. -Jason Fauchelle |
|
|
|
|
Hi Jason, I download the April. 21, 2014 nightly build and the crash is still there. We really need these to be fixed. Thanks, Gordon |
|
|
|
|
Hello Gordon I've put checks in the next most likely places that an issue can occur. This will be available in the next nightly build. If the issue remains - which is unlikely - please send the list of data at the point of the crash as well as the values of LabelStep, LabelLevelCount and MajorTickMarkSpacing on the independent axis. -Jason Fauchelle |
|
|
|
|
Seems it is fixed. Thx, Gordon |
|
|
|
