Re: Adjusting to new NoesisGUI release for Unity
Posted: 30 Sep 2022, 09:31
Probably. Please humor me a bit and then I might end up just using the thread to talk to myself this weekend afterwards. I increased the verbosity and it was at least telling me what successfully loaded beforehand. I can see my theme.xaml was loaded. Right after that, it complains about not finding B.xaml. It's all happening within A's codebehind in LoadComponent.
I think what that at least tells me is the theme is probably not the culprit. That's good because at lot of the theme is kind of yoinked. Well, I shouldn't be surprised then because it isn't like I have it referencing controls and stuff; it shouldn't be the problem.
I guess at this point I can just kind of go through all the names of things in the xaml, make a list of theme, and find their provenance. The view model was already ripped out into a separate file and didn't need to directly referencing any Xaml (which I should assume is a good and correct thing). So maybe I just have some term that's dragging in B.xaml somehow through namespaces (?).
Personally I'm surprised it's finding something it apparently is convinced it needs from B.xaml without me having done anything directly in A.xaml to say that file even exists. But B.xaml kind of describes the parent control so they do have at least an implicit association.
You know the problem with descriptive code like XAML is you can't just, like, shove some print statements in it and see where it croaks. :p
I think what that at least tells me is the theme is probably not the culprit. That's good because at lot of the theme is kind of yoinked. Well, I shouldn't be surprised then because it isn't like I have it referencing controls and stuff; it shouldn't be the problem.
I guess at this point I can just kind of go through all the names of things in the xaml, make a list of theme, and find their provenance. The view model was already ripped out into a separate file and didn't need to directly referencing any Xaml (which I should assume is a good and correct thing). So maybe I just have some term that's dragging in B.xaml somehow through namespaces (?).
Personally I'm surprised it's finding something it apparently is convinced it needs from B.xaml without me having done anything directly in A.xaml to say that file even exists. But B.xaml kind of describes the parent control so they do have at least an implicit association.
You know the problem with descriptive code like XAML is you can't just, like, shove some print statements in it and see where it croaks. :p