Search found 12 matches
- 26 Nov 2025, 17:18
- Forum: General Discussion
- Replies: 2
- Views: 6082
Re: Serialization of Noesis Object tree to XAML
That is something I was afraid of.
Anyway, thank you very much for that information.
Anyway, thank you very much for that information.
- 26 Nov 2025, 09:25
- Forum: General Discussion
- Replies: 2
- Views: 6082
Serialization of Noesis Object tree to XAML
Hey,
I want to ask you if there is any way to serialize Noesis object tree that is loaded to application memory back to XAML?
I'm asking because I want to made some runtime changes to some objects using Noesis API and and then save it back to XAML if possible.
Any help will be appreciated :)
I want to ask you if there is any way to serialize Noesis object tree that is loaded to application memory back to XAML?
I'm asking because I want to made some runtime changes to some objects using Noesis API and and then save it back to XAML if possible.
Any help will be appreciated :)
- 10 Sep 2025, 09:08
- Forum: General Discussion
- Replies: 4
- Views: 5788
Re: Problem with UI thread (cannot access this Border because a different thread owns it)
Ok, it looks that loading default styles also needs to be done on UI thread. That's the reason.
- 09 Sep 2025, 12:24
- Forum: General Discussion
- Replies: 4
- Views: 5788
Re: Problem with UI thread (cannot access this Border because a different thread owns it)
I'm tried with that piece of code executed on my UI thread. m_queue->syncTask<void>([this]() { Noesis::Ptr<Noesis::FrameworkElement> xaml = Noesis::GUI::LoadXaml<Noesis::FrameworkElement>(m_xamlResource->resourcePath().c_str()); auto view = Noesis::GUI::CreateView(xaml); view->SetSize(1920, 1080); }...
- 09 Sep 2025, 11:42
- Forum: General Discussion
- Replies: 4
- Views: 5788
Re: Problem with UI thread (cannot access this Border because a different thread owns it)
Xaml I use to view creation has good thread id. LoadXaml is called just before CreateView function on the same dedicated thread. The error appears when I want to execute view->SetSize(size.x, size.y) function later in some frame stuff scope.
- 09 Sep 2025, 10:02
- Forum: General Discussion
- Replies: 4
- Views: 5788
Problem with UI thread (cannot access this Border because a different thread owns it)
I'm trying to integrate more and more stuff from Noesis to custom engine. Currently I have problem with threading. My engine uses different workers to initialize and then update many systems. One of them is UI system (Noesis). So due to there are many different threads, Noesis comes with ERROR that ...
- 04 Jul 2025, 12:11
- Forum: Noesis Studio
- Replies: 3
- Views: 19595
Re: [NOESIS/E] MainWindow.xaml(14,9): Unknown element type 'Component'
Nevermind, I've just found on forum that this is Noesis Studio only extension for now. Sorry for duplicating.
- 04 Jul 2025, 12:07
- Forum: Noesis Studio
- Replies: 3
- Views: 19595
[NOESIS/E] MainWindow.xaml(14,9): Unknown element type 'Component'
I created simple <Component> element in separate xaml file with Noesis Studio and trying to use it in SDK. Every changes I made in HelloWorld project in NoesisGUI-NativeSDK-win-3.2.7-Indie: - I added testComponent.xaml in Data directory and add it to project with Custom Build step to generate embedd...
- 03 Jul 2025, 16:54
- Forum: General Discussion
- Replies: 5
- Views: 15928
Re: Max number of offscreen surfaces reached
Thank you for your answer. Yes, I already get it that these surfaces are mipmap pyramid, but thanks for clarification. It appears that SetOffscreenMaxNumSurfaces was set to 2. So in our case it seems to low. Sorry, I cannot share RenderDoc.
- 25 Jun 2025, 11:30
- Forum: General Discussion
- Replies: 5
- Views: 15928
Re: Max number of offscreen surfaces reached
I also have set SetOffscreenMaxNumSurfaces to 2, and try different numbers, but doesn't change anything