Forums | NoesisGUI

Hi everyone,

I'm working on a NoesisGUI project with a fairly large list of UI elements and I'm starting to notice some performance drops when the underlying data changes frequently.

Is there a recommended approach for minimizing the cost of updating bindings when many properties can change at once? I'm particularly interested in whether it's better to batch the updates, replace the collection, or rely on INotifyPropertyChanged for individual items.

I'm currently using C++ with XAML, so any advice or examples of patterns that work well in NoesisGUI would be greatly appreciated.

Thanks!

In my experience, batching related changes and using INotifyPropertyChanged for individual properties is usually more efficient than repeatedly replacing the whole collection, especially with larger lists.

I'm working on a NoesisGUI project with a fairly large list of UI elements and I'm starting to notice some performance drops when the underlying data changes frequently.

For better performance, it is very important not to refill the entire list. Instead, you should only add or remove the items that have actually changed and properly notify the UI through INotifyCollectionChanged.

Could you please provide more information about the performance issues you're experiencing?