This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi All, XAML: } |
|
|
It looks like there's an error in the CLR wrapper event which is causing Visual Studio to generate the wrong signature for the event handler. Can you try changing ToolDroppedEventArgs to DiagramNodeToolDroppedEventArgs in the handler signature and see if that helps? |
|
|
Hi Ivan, Thanks for the reply. It does recognize the DiagramNodeToolDroppedEventArgs class as existing, but if I change the paraemter to that I get this error: No overload for 'DiagramNodeTool_DiagramNodeToolDropped' matches delegate 'System.EventHandler<Mindscape.WpfDiagramming.Foundation.ToolDroppedEventArgs>' |
|
|
Hmm, I believe this is still the bug at our end. We can get you a fix in the nightly build, or if you just want to get on then you should be able to bypass the erroneous CLR event handler and write (in the .xaml.cs file): tool.AddHandler(DiagramNodeTool.DiagramNodeToolDroppedEvent, DiagramNodeTool_DiagramNodeToolDropped); (You will still need to keep the updated event handler function signature, and to remove the event reference from your XAML.) |
|
|
I'll just wait for the fix in the nightly build. Adding the event that way does allow the program to compile, but the event never fires so I suspect something else is wrong. |
|