Thanks for quick response,
I've investigated some tricks, and found that I can put a <Path ... ... > in the XAML markup and bind his Data property to a string containing the path coordinates in "mini language" as "Mx,y Lx1,y1 x2,y2 x3,y3 ...".
But neither this way is working at runtime, even if directly writing the Path markup in the XAML is effectively working (
the thickness is ignored, though).
So I tried to investigate more, via Reflector, and at some point I encounter this line in the decompiled BindingExpression.cs:
- MAP-0035.jpg (201.73 KiB) Viewed 12761 times
There is two absign, I don't know if this is a result of poor decompilation, but I think it's not correct. There is no reason to assign to "walker" a boolean value x=y=z is x=(y=z) .
edit: Obviously it's not true, sorry: x=y=z is not like x = y == z, so the code is correct,
but in fact it refers to object that are null at runtime: a "Null reference" error is coming from that line, and if I correct the line deleting "= this.PropertyWalker" I again obtain a null reference, but the reason is that binding.INTERNAL_ComputedPath is null.
So I can't find a way to draw a path programatically and that is the only mandatory visual thing I need to implement.
I hope I've give you a clue for fixing.
Flavio