I'm using the XamPivotGrid and its performance is a huge problem. In order to workaround this issue i want to know if there's a way to avoid that the user clicks in multiple cells(expanding it) one after another.
It is possible to disable the interaction while the previous expansion results are not rendered?
Regards,
Ângelo.
Hello,
Which version of the control you have? You can look at this sample. You can track the changes of DataSourceBase.Processing property so you can bind the visibility of some element to it and in this way you can achieve something like " is busy" indicator. Also with the latest service releases there is a property named IsBusy which duplicates the Processing property.
Regards.Plamen.
Hi,
I'd already implemented that solution. But the problem is that between the click on the expansion button, and the notification of the "IsProcessing" property change theres a very big period of time.
Is there some other way?
Thanks for the quick answer,
Ângelo Moreira.
Hi
The names are the same, but version is 11.1. I mean if you have xxx.v10.3.dll replace with xxx.v11.1.dll
Todor
Hi and thanks,
I'd already performed all the changes. The API changs are just a few. But when i run the aplication i alwyas get the exception: System.Windows.Markup.XamlParseException: Element is already the child of another element. [Line: 0 Position: 0]
Is there any other think that i should have in mind whem performing this update?
Could you provide us the initialization code you have if any?
Plamen.
Just this (some properties initialization and a timer)
this
.ColumnSpan = 5;
Could you paste your code in Word first and then copy it again and paste it to the post text box.
Sure, it was a mistake!
-----------------------------
InitializeComponent(); this.ColumnSpan = 5; this.RowSpan = 5; this.isBusyTimer = new DispatcherTimer(); this.isBusyTimer.Interval = new TimeSpan(0, 0, 0, 0, 500); this.isBusyTimer.Tick += new EventHandler(this.IsBusyTimer_Tick);
Once i had a similar problem in the version 10.3. The answer was on the styles. This time i'm not understending.