Thanks for writing back and for the feedback on the new behavior related to using the IsAsyncBalanceEnabled
After updating the behavior related to setting this property to true
, we haven't noticed any performance and UX issues in our Demos Application.
In other words, the RadDataBoundListBox
demos which we tested after that deliver pretty much the same user experience. We haven't noticed any performance hits in your application too besides the fact that the animation played on the ItemStateChanged
event is no more visible (which is expected behavior). In general, generating 3-5 visual items at once (to fill the viewport) should not be a time consuming operation. Could you please try the same scenario without hooking the ItemStateChanged
event and playing the animation. This might decrease the startup time since the event is fired synchronously each time a new visual item is created and thus requires additional time.
Otherwise we will consider your notes on the asynchronous balance approach and will discuss possibilities for improving its behavior. For instance a possible way of handling this functionality would be to fill the viewport synchronously and after that use an async way of realizing items by default (i.e. when the IsAsyncBalanceEnabled
is set to false
). When the IsAsyncBalanceEnabled
is set to true the behavior will be for each item, i.e. without considerations whether the viewport is filled or not.
I hope this is helpful.
Do not hesitate to get back to us in case you have further questions or need assistance.
the Telerik team
Let us know about your Windows Phone 7 application built with RadControls and we will help you promote it. Learn more>>