tag:blogger.com,1999:blog-959852766553998174.post5112587338591287906..comments2023-03-23T06:08:05.289-04:00Comments on WPF Tips: WPF Tip #1 - IsAsync and WPF BindingsAlvin Ashcrafthttp://www.blogger.com/profile/04705298386808338562noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-959852766553998174.post-36267269261532583682019-04-29T09:30:21.711-04:002019-04-29T09:30:21.711-04:00It depends. If the child item's data is changi...It depends. If the child item's data is changing at a point where the collection is not changing, then there could be a bottleneck there. If the items in the collection only update their properties when the collection is changing (or any properties of the individual properties update very quickly), then this method will be fine. Otherwise, you might want to consider adding IsAsync to the other props.Alvin Ashcrafthttps://www.blogger.com/profile/04705298386808338562noreply@blogger.comtag:blogger.com,1999:blog-959852766553998174.post-58963389789399317882019-04-23T12:52:36.494-04:002019-04-23T12:52:36.494-04:00Does the IsAsync-ness cascade to child bindings? ...Does the IsAsync-ness cascade to child bindings? For example, your main ListView ItemsSource binding to MediaCatalog is async, but you have sub-bindings to Artist, Title, etc. that aren't marked as IsAsync=True. Will those sub-bindings still be a bottleneck?Vargohttps://www.blogger.com/profile/13679062624139257360noreply@blogger.com