Hi ,
i want to create a line chart , where i can drag the line using the mouse and modify the graph doing so.
i am using MVVM , so i would like each mouse drag to change my VM data. so i can use it later .
is this supported by XamDatachart ?
if so, can i get a small example or a link ?
Thanks.
I have updated the sample to netcore50, its more relevant to whomever needs this solution.
xamDataChart-DragLineSeriesData.zip
Hi Rob,
thank you for the hints.
The Problem was that your sample Project was built against .NET Framework Version 4.0 while the Interaction assembly was built agains Version 4.5.
Setting the target Framework of the sample Project to 4.61 solved the Problem.
Regards Horst
It is an old sample so I'm not surprised it targets 4.0 but I should have realized what versions of .NET everything was targeting. I'll keep that in mind the next time I need to update older samples. I'm glad you were able to figure it out and resolve it though. Awesome!
thank you for the stackoverflow link. The last entry let me to the solution...
scolling down the list showed an entry that System.Windows,Interactivity was built against .NET 4.5.
The sample Project was built against 4.0 Client. Thus selecting 4.61 as target Framework and rebuilt, solved the Problem.
Hi Horst,
I'm not really sure what the issue could be then if you have all the assemblies required. That stackoverflow issue deals more with using Interaction.Behavior inside a Resource tag which this sample does not do.
I can also see in your screenshot that there are more errors for other objects as well. Have you tried to build the project regardless of those errors? In some cases the XAML designer is known to display errors but the project is still capable of building and running successfully.
You could also try some of the solutions listed here: https://stackoverflow.com/questions/14665713/the-name-does-not-exist-in-the-namespace-error-in-xaml
But if you can still build and run the project regardless of those designer errors then I wouldn't worry about it too much for this sample. The designer isn't useful in this scenario. The important parts are in the behavior itself at how it attaches to the chart series.