Noesis Questions
Posted: 26 Jun 2018, 15:48
I program a simulation called Run8. We've used WPF for our menus for quite a long time, but of course one can't render WPF in true Fullscreen. SInce we really need to use true fullscreen and not the borderless-window method we've been using, I've been trying Noesis to see if it would suit our needs, and mostly it works great. This is a DotNet Windows application using DirectX11 via SharpDX, C#, and VisualStudio 2015/2017.
I have some issues though, and I don't know if it's me, Visual-Studio, or Noesis:
1) Visual Studio 2017 is constantly giving me "The type XYZ does not support direct content". 'XYZ' can be a Border, Trigger, UserControl, Storyboard, etc. I have searched and searched for a solution to no avail. The code compiles and runs just fine though, but my editor is spammed with blue squiggly underlines everywhere. This happens for any of the menus I've converted into Noesis, which all seem to compile and function perfectly fine in-game.
2) Using the sample NumericUpDown (I literally cut and pasted the code and changed the namespace where needed), I was once and only once able to place it into my menu and edit it. Ever since then, I'm plagued with "Invalid Markup" even though everything compiles and runs just fine, with the NumericUpDown showing and operating normally in the simulation. In VS2017, if I comment-out the NumericUpDown, I get my designer back, and when I uncomment, I'm right back to Invalid Markup and can't edit the menu.
-This also happens if I use Blend for 2017.
-I was getting a namespace error, even though I know for absolute certain the namespace was just fine in all the places it needed to be, and in-game, all runs fine
-I also get "The specified value cannot be assigned to in the collection. The following type was expected: "UIElement".
-And "The attached property "Left" or "Top" can only be applied to types that are derived from "UIElement"; relating to Canvas.Left and Canvas.Top in the NumericUpDown
3) The GroupBox that shows in VS2017 doesn't match what shows in the simulation, and I cannot figure out why nor how to remedy that.
4) Question: In our WPF menus, we had our own style for GroupBoxes that got rid of that ugly double-white border and allowed us to have the header along the top of the border. Unfortunately it uses a Multibinding entry to take care of the mask that blanks out the portion of the border under the header, which Noesis doesn't seem to like. How would I go about getting something like that to work in Noesis?
Thanks in advance, and overall I'm impressed! I just need to sort out these things before I can commit. I also have a licensing question, but that can wait till later.
John G.
I have some issues though, and I don't know if it's me, Visual-Studio, or Noesis:
1) Visual Studio 2017 is constantly giving me "The type XYZ does not support direct content". 'XYZ' can be a Border, Trigger, UserControl, Storyboard, etc. I have searched and searched for a solution to no avail. The code compiles and runs just fine though, but my editor is spammed with blue squiggly underlines everywhere. This happens for any of the menus I've converted into Noesis, which all seem to compile and function perfectly fine in-game.
2) Using the sample NumericUpDown (I literally cut and pasted the code and changed the namespace where needed), I was once and only once able to place it into my menu and edit it. Ever since then, I'm plagued with "Invalid Markup" even though everything compiles and runs just fine, with the NumericUpDown showing and operating normally in the simulation. In VS2017, if I comment-out the NumericUpDown, I get my designer back, and when I uncomment, I'm right back to Invalid Markup and can't edit the menu.
-This also happens if I use Blend for 2017.
-I was getting a namespace error, even though I know for absolute certain the namespace was just fine in all the places it needed to be, and in-game, all runs fine
-I also get "The specified value cannot be assigned to in the collection. The following type was expected: "UIElement".
-And "The attached property "Left" or "Top" can only be applied to types that are derived from "UIElement"; relating to Canvas.Left and Canvas.Top in the NumericUpDown
3) The GroupBox that shows in VS2017 doesn't match what shows in the simulation, and I cannot figure out why nor how to remedy that.
4) Question: In our WPF menus, we had our own style for GroupBoxes that got rid of that ugly double-white border and allowed us to have the header along the top of the border. Unfortunately it uses a Multibinding entry to take care of the mask that blanks out the portion of the border under the header, which Noesis doesn't seem to like. How would I go about getting something like that to work in Noesis?
Thanks in advance, and overall I'm impressed! I just need to sort out these things before I can commit. I also have a licensing question, but that can wait till later.
John G.