Zero Gravity Chimp
Top achievements
Rank 2
Rank 2
Zero Gravity Chimp
asked on 21 Jan 2010, 11:05 PM
Hello,
I've posted part of my problem, but could not rename the thread:
http://www.telerik.com/community/forums/silverlight/chart/backgroundworker-for-radchart.aspx
I hope that this title will promote discussion on the topic - I think everyone needs this? let me know if i'm wrong to have opened a new thread.
As performance goes many people are complaining about the data updating and something has been mentioned for Q1 2010 or later on as a fix.
I would just like to clarify that I am not interested in increasing the performance speed of the chart, but I want to increase the performance and usability of my entire application by separating the chart's processing from the UI thread. this is very important for our project.
The chart could take 20 milliseconds to populate or it could take 2000 with one hundred times more data. Even if it takes a full minute, there must be a way that this can be done which does not lock up the UI thread.
For clarification and help in answering my query, as I understand UI thread it is the main processing stream of the application, which controls animations and all of my usercontrol processing, like button-clicks and their events, mouse over events and effects, et cetera. When the chart (or many charts) are busy working, this thread is overloaded and clicks, mouseovers, and event handlers are not working correctly.
If necessary I could set up a test project for this, but I'm sure everyone understands the 'freezing' effect that I am referring to, which can be seen in animations being jerky and the nonresponsiveness of the application.
Thanks a lot,
Chimp
I've posted part of my problem, but could not rename the thread:
http://www.telerik.com/community/forums/silverlight/chart/backgroundworker-for-radchart.aspx
I hope that this title will promote discussion on the topic - I think everyone needs this? let me know if i'm wrong to have opened a new thread.
As performance goes many people are complaining about the data updating and something has been mentioned for Q1 2010 or later on as a fix.
I would just like to clarify that I am not interested in increasing the performance speed of the chart, but I want to increase the performance and usability of my entire application by separating the chart's processing from the UI thread. this is very important for our project.
The chart could take 20 milliseconds to populate or it could take 2000 with one hundred times more data. Even if it takes a full minute, there must be a way that this can be done which does not lock up the UI thread.
For clarification and help in answering my query, as I understand UI thread it is the main processing stream of the application, which controls animations and all of my usercontrol processing, like button-clicks and their events, mouse over events and effects, et cetera. When the chart (or many charts) are busy working, this thread is overloaded and clicks, mouseovers, and event handlers are not working correctly.
If necessary I could set up a test project for this, but I'm sure everyone understands the 'freezing' effect that I am referring to, which can be seen in animations being jerky and the nonresponsiveness of the application.
Thanks a lot,
Chimp
2 Answers, 1 is accepted
0
Zero Gravity Chimp
Top achievements
Rank 2
Rank 2
answered on 22 Jan 2010, 01:57 AM
Hi, just a follow up,
I've checked again and it seems that in most or all cases mouse clicks are being registered and handled and the same for mouse over is assumed. Animations do freeze though.
When comparing two scenarios, one where i am assigning a collection to the 'itemssource' property of the chart, and the other where i'm doing all the same processing without assigning the collection, the difference is obvious and animations can be seen to freeze in mid-movement.
Regards,
Paul
I've checked again and it seems that in most or all cases mouse clicks are being registered and handled and the same for mouse over is assumed. Animations do freeze though.
When comparing two scenarios, one where i am assigning a collection to the 'itemssource' property of the chart, and the other where i'm doing all the same processing without assigning the collection, the difference is obvious and animations can be seen to freeze in mid-movement.
Regards,
Paul
0
Accepted
Hi Zero Gravity Chimp,
As I already wrote in another thread, Silverlight does have a single UI thread and, unfortunately, most of the controls' work should happen there.
In WPF there is a way to create multiple UI threads (creating multiple new windows), but no such option is available in Silverlight.
All the best,
Evtim
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
As I already wrote in another thread, Silverlight does have a single UI thread and, unfortunately, most of the controls' work should happen there.
In WPF there is a way to create multiple UI threads (creating multiple new windows), but no such option is available in Silverlight.
All the best,
Evtim
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.