Xceed Community - Scrolling in Cardflow 3D View too fast crashes app

sales.europe@xceed.com

support.europe@xceed.com

Welcome to the Xceed Community | Help

Community Search
More Search Options

Xceed Community » WPF and Silverlight Controls » Xceed DataGrid for WPF » Scrolling in Cardflow 3D View too fast crashes app

Scrolling in Cardflow 3D View too fast crashes app


	Sort Posts: Previous Next

07-28-2010, 2:40 PM Post no. 27777

carlos
Joined on 09-23-2008
Posts 9

Scrolling in Cardflow 3D View too fast crashes app

When scrolling back to the beginning card of the view quickly (dragging on the scroll bar back and forth), the grid throws an exception and crashes the application both in Visual Studio 2008/2010 and using the Xceed WPF binaries for versions 3.7 and 4.0.

The exception I receive is:

InvalidOperationException (Specified element is already the logical child

of another element. Disconnect it first.) was unhandled ... with the

following stacktrace:

at System.Windows.FrameworkElement.ChangeLogicalParent(DependencyObject

newParent)

at System.Windows.FrameworkElement.AddLogicalChild(Object child)

System.Windows.Controls.ContentControl.OnContentChanged(DependencyObject d,

DependencyPropertyChangedEventArgs e)

at System.Windows.PropertyChangedCallback.Invoke(DependencyObject d,

DependencyPropertyChangedEventArgs e)

System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs

System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs

System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs

args)

at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex

entryIndex, DependencyProperty dp, PropertyMetadata metadata,

EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean

coerceWithDeferredReference, OperationType operationType)

System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp)

at System.Windows.Data.BindingExpression.Invalidate(Boolean

isASubPropertyChange)

at System.Windows.Data.BindingExpression.TransferValue(Object newValue,

Boolean isASubPropertyChange)

at System.Windows.Data.BindingExpression.Activate(Object item)

System.Windows.Data.BindingExpression.HandlePropertyInvalidation(DependencyObject

d, DependencyPropertyChangedEventArgs args)

System.Windows.Data.BindingExpression.OnPropertyInvalidation(DependencyObject

d, DependencyPropertyChangedEventArgs args)

at System.Windows.DependentList.InvalidateDependents(DependencyObject

source, DependencyPropertyChangedEventArgs sourceArgs)

System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs

args)

at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex

entryIndex, DependencyProperty dp, PropertyMetadata metadata,

EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean

coerceWithDeferredReference, OperationType operationType)

at System.Windows.DependencyObject.SetValueCommon(DependencyProperty

dp, Object value, PropertyMetadata metadata, Boolean

coerceWithDeferredReference, OperationType operationType, Boolean

isInternal)

at System.Windows.DependencyObject.SetValue(DependencyProperty dp,

Object value)

at System.Windows.FrameworkElement.set_DataContext(Object value)

at Xceed.Wpf.DataGrid.Cell.AssignDataContext(Cell cell, Object

dataContext, ColumnBase parentColumn, Boolean& isNewDataContext)

at Xceed.Wpf.DataGrid.Cell.PrepareContainer(DataGridContext

dataGridContext, Object item)

at Xceed.Wpf.DataGrid.DataCell.PrepareContainer(DataGridContext

dataGridContext, Object item)

at Xceed.Wpf.DataGrid.Row.PrepareContainer(DataGridContext

dataGridContext, Object item)

at Xceed.Wpf.DataGrid.DataRow.PrepareContainer(DataGridContext

dataGridContext, Object item)

Xceed.Wpf.DataGrid.Row.Xceed.Wpf.DataGrid.IDataGridItemContainer.PrepareContainer(DataGridContext

dataGridContext, Object item)

Xceed.Wpf.DataGrid.DataGridControl.PrepareContainerForItemOverride(DependencyObject

element, Object item)

Xceed.Wpf.DataGrid.DataGridControl.PrepareItemContainer(DependencyObject

container, Object item)

Xceed.Wpf.DataGrid.CustomItemContainerGenerator.System.Windows.Controls.Primitives.IItemContainerGenerator.PrepareItemContainer(DependencyObject

container)

at Xceed.Wpf.DataGrid.Views.CardflowItemsHost.GenerateContainers()

at Xceed.Wpf.DataGrid.Views.CardflowItemsHost.GeneratorTimerTick(Object

sender, EventArgs e)

at System.Windows.Threading.DispatcherTimer.FireTick(Object unused)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate

callback, Object args, Boolean isSingleParameter)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object

source, Delegate callback, Object args, Boolean isSingleParameter, Delegate

catchHandler)

at System.Windows.Threading.DispatcherOperation.InvokeImpl()

at System.Threading.ExecutionContext.runTryCode(Object userData)

System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode

code, CleanupCode backoutCode, Object userData)

at System.Threading.ExecutionContext.Run(ExecutionContext

executionContext, ContextCallback callback, Object state)

at System.Windows.Threading.DispatcherOperation.Invoke()

at System.Windows.Threading.Dispatcher.ProcessQueue()

at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32

msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam,

IntPtr lParam, Boolean& handled)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate

callback, Object args, Boolean isSingleParameter)

at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object

source, Delegate callback, Object args, Boolean isSingleParameter, Delegate

catchHandler)

at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority

priority, TimeSpan timeout, Delegate method, Object args, Boolean

isSingleParameter)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr

wParam, IntPtr lParam)

at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(MSG&

msg)

at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame

frame)

at System.Windows.Application.RunInternal(Window window)

at FarsightAlphaUserInterface.Application.Main() in

C:\Users\Vivien\Documents\Visual Studio

2008\Projects\FarSight\prototypes\FarsightAlphaUserInterface\obj\Debug\Application.g.vb:line

at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)

at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

at System.Threading.ExecutionContext.Run(ExecutionContext

executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

Filed under: Cardflow, Cardflow3d, Cardview datagrid, CardflowView3D

Report abuse

08-01-2010, 2:33 PM Post no. 27841 in reply to 27777

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

Is anybody else experience this problem with the Cardflow 3D??

Report abuse

08-02-2010, 12:24 PM Post no. 27853 in reply to 27841

Diane [Xceed]
Joined on 12-29-2008
Boucherville, QC
Posts 938

Re: Scrolling in Cardflow 3D View too fast crashes app

Hi Carlos,

We are aware of this issue. The development team has a fix request open to correct it. We will post an update in this forum thread to inform you when the fix becomes available. Thank you for your patience.

Diane Lafontaine
Technical Support / Technical Support Team Lead
Xceed Software Inc.

Report abuse

08-09-2010, 2:39 PM Post no. 27925 in reply to 27853

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

Is there an ETA for this fix?

Carlos

Report abuse

08-09-2010, 3:44 PM Post no. 27926 in reply to 27925

Diane [Xceed]
Joined on 12-29-2008
Boucherville, QC
Posts 938

Re: Scrolling in Cardflow 3D View too fast crashes app

Hi Carlos,

The fix request is currently assigned to a developer, and our goal is to have it fixed in the next service release (currently planned in 2 weeks).

Diane Lafontaine
Technical Support / Technical Support Team Lead
Xceed Software Inc.

Report abuse

08-13-2010, 12:39 PM Post no. 27976 in reply to 27926

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

Looking forward to the fix, thanks.

Carlos

Report abuse

08-21-2010, 2:19 PM Post no. 28034 in reply to 27976

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

Still waiting for the fix, but I had a question about catching this exception in the meanwhile.

I am a fairly experience .net developer, but I can't figure out how to catch this exception. I already went into Debug | Exceptions and checked both boxes under Common Language Runtime Excetions (actually I check all the boxes) and still I don't get the line number where this is crashing in my code? Is there a place where I can handle this exception (or any other exception that may come up in the future)? I don't want my users to experience a crash. I would like to put a friendlier message and re-initialize things.

Does anybody know how to do this?

Thanks in advance!

Carlos

Report abuse

08-21-2010, 3:01 PM Post no. 28035 in reply to 28034

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

This worked for me as far as catching the error and being able to end the program gracefully.

http://xceed.com/CS/forums/post/21388.aspx

Carlos

Report abuse

08-30-2010, 3:51 PM Post no. 28106 in reply to 28035

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

Was this fixed with: 4.0.10417.16400 released August 23, 2010???

Report abuse

09-01-2010, 2:57 PM Post no. 28551 in reply to 28106

Diane [Xceed]
Joined on 12-29-2008
Boucherville, QC
Posts 938

Re: Scrolling in Cardflow 3D View too fast crashes app

Hi Carlos,

Unfortunately, this issue has not yet been fixed. We apologize for the inconvenience.

We will post an update in this forum thread when the fix does become available. Thank you for your patience.

Diane Lafontaine
Technical Support / Technical Support Team Lead
Xceed Software Inc.

Report abuse

10-07-2010, 11:44 AM Post no. 28931 in reply to 28551

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

What's the status on this? Is it fixed yet? Do you have an ETA?

Carlos

Report abuse

11-05-2010, 4:48 PM Post no. 29150 in reply to 28931

Diane [Xceed]
Joined on 12-29-2008
Boucherville, QC
Posts 938

Re: Scrolling in Cardflow 3D View too fast crashes app

Attachment: 133967.zip

Hi Carlos,

Unfortunately, the priority on this fix request was lowered due to other more pressing issues that needed attention, and also because a workaround had been provided to you by email (you were in CC in our reply to Vivien in support case 133967).

For reference, here is the answer we had provided:

----

After further investigation, the developer noticed that you are using a UIElement in your BusinessObject. That is a bad practice as a UIElement cannot be at two places at once, which is causing the crash in the 3D View.

While we may still have a bug on our end, it would be easy for you to avoid this crash if instead of storing in your business object a System.Windows.Controls.Image, you stored a byte array, or even a string representing the URI with a CellContentTemplate that would use an Image with the value of the property as its source.

As an example, please find attached a project that demonstrates the byte array solution, and where the crash no longer occurs.

----

At this time, there is no known ETA in regards to this fix request.

Diane Lafontaine
Technical Support / Technical Support Team Lead
Xceed Software Inc.

Report abuse

11-12-2010, 1:53 PM Post no. 29213 in reply to 29150

carlos
Joined on 09-23-2008
Posts 9

Re: Scrolling in Cardflow 3D View too fast crashes app

I took a look at your workaround and I still feel that you need to do something here.

We are not just dropping images into the grid, we are marrying it with other information as well and we ARE using a byte array in our latest code.

The problem is still present.

Your case is pretty simple and doesn't account for a more complex cases. For right now we are forced to hide the errors that come up and I guess that will have to do until you address the real problem or people compel you to raise the priority. Until then, we will be looking at alternatives.

I did appreciate you looking into this though. Thanks.

Carlos

Report abuse