Please, do not resurrect old threads that are marked as solved. Create new ones. Thanks!

ok,sorry,i just want to bookmark it. just find the function;

Our application framework is setup to render continuously everything per frame. This is the common scenario in videogames. But you can avoid that in your own integration if you want. See for example the IRenderer interface: /// Applies last changes happened in the view. This function does not inter...

Each UserControl is defined in separate xaml files, then you can reference them in any other xaml just by including an instance of the code-behind class: MyUserControl.xaml <UserControl x:Class="Testing.MyUserControl" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http:/...

In MVVM you will expose an ObservableCollection for the items, and changes done to that collection will reflect in the UI. In order to notify of changes in the data items so UI can be automatically updated, your data must implement the INotifyPropertyChanged interface. You can read more about this ...

Noesis does not implement a File browser dialog. You can directly use an operating system dialog (via Win32 in Windows for example), or you can create your own UserControl to render it using Noesis inside your window.

ok,thanks

for example win32 api: SHBrowseForFolder
do I need to implement it by myself?

usercontrol has to put in mainwindow.xml?

I don't understand the question, could you please elaborate a bit more?

I mean each usercontrols will put in a different .xaml file?

Iunderstand thanks。could put to a new xaml file

Yes, we have VirtualizingStackPanel implemented and it is the default items panel for ListBox and ListView. You can also manually use it any ItemsControl by specifying it in the ItemsPanel property. This means only visible items are generated and layout, so you can load lists with hundreds of items...

Collapsed controls are not processed during layout so they don't affect the performance.
Although the elements in that tree will be initially created, so the memory consumption will be bigger when having all the screens defined in the main window.

i see, thanks

Yes, we have VirtualizingStackPanel implemented and it is the default items panel for ListBox and ListView. You can also manually use it any ItemsControl by specifying it in the ItemsPanel property. This means only visible items are generated and layout, so you can load lists with hundreds of items...