Re: Caliburn.Micro port issues
Posted: 27 Feb 2017, 18:21
Man this is so cool what you are doing, if these things would get patched it should increase the compatibility between WPF and NoesisGUI a lot.
Welcome to our official discussion site. You’ll find topics on features, bugs, development, and general support here
https://www.noesisengine.com/forums/
var boder = new Border { Background = Brushes.Silver };
var stack = new StackPanel { Orientation = Orientation.Horizontal };
var text1 = new TextBlock { Text = "Name: " };
var text2 = new TextBlock();
stack.Children.Add(text1);
stack.Children.Add(text2);
border.Child = stack;
var dataTemplate = new DataTemplate { VisualTree = border };
Assertion failed: Assertion failed on expression: '!performAutorepaint || GetApplication().MayUpdate()'
UnityEditor.AssetDatabase:SaveAssets()
NoesisPostprocessor:OnPostprocessAllAssets(String[], String[], String[], String[]) (at Assets/NoesisGUI/Plugins/Editor/NoesisPostprocessor.cs:55)
UnityEditor.AssetPostprocessingInternal:PostprocessAllAssets(String[], String[], String[], String[], String[])
When are you getting this? Does it happen with a clean installation of our package?First and foremost I'm still getting the
error all over the place. What's the deal with this?Code: Select allAssertion failed: Assertion failed on expression: '!performAutorepaint || GetApplication().MayUpdate()' UnityEditor.AssetDatabase:SaveAssets() NoesisPostprocessor:OnPostprocessAllAssets(String[], String[], String[], String[]) (at Assets/NoesisGUI/Plugins/Editor/NoesisPostprocessor.cs:55) UnityEditor.AssetPostprocessingInternal:PostprocessAllAssets(String[], String[], String[], String[], String[])
One of the examples included in the package (Start menu) is just a bunch of DelegateCommands connected to buttons. Could you please have a look at it?I also tried using DelegateCommand from the Noesis.Samples since Caliburn Actions don't work yet, but that doesn't seem to do anything at all when I bind it to a Button Command.
Yes, but less and less with each version. Thanks a lot for your work, please let us know how we can help you.I'll have to look into this further but so far... there seem to be still a lot of incompatibilities to WPF.