Hi

In our scenario, we have a parent diagram holding multiple UIElements, each containing a diagram (this has the potential to have further depths). 

How would I go about ensuring a UIelement in one of the sub diagrams receives the mouse / stylus events, rather than (in the case of the mouse move event) the adaptor node reacting to the input and moving the node?

The following is a basic description of objects involved and thier level of nesting:

Diagram --> Diagram Adaptor --> UIElement --> Diagram --> Diagram adaptor --> UIElement --> Slider control


I initially thought I could do this by handling events like MouseDown, MouseUp MouseEnter and MouseLeave MouseMove but I found that some events caused others to fire out of sequence and broke the logic.


Any suggestions welcome.



Many thanks


Paul

We are implementing the same scenario as Paul, where we have multiple UIElements, each of which contains a Diagram instance.

We're having trouble with de-serializing the diagram when reloading it from an Xml file. It seems that certain read-only properties of the child diagram get serialized, and cannot be reinitialized when the parent diagram is reloaded.

Can anyone suggest how to implement this embedded scenario? Should we make the nested diagram a Tag of the UIElement and handle the serialization manually?

Thanks,

Greg

That would be helpful.

As a workaround, we're assigning the nested diagram to the Tag property of our control's parent DiagramNodeAdapter. That way, it gets serialized with the parent diagram.

The problem we're having now is that once we've deserialized the child diagram, we assign it to an instance of the Page class (we're taking the same approach is was done in the FCDemo sample); but we can't rebuild the visual tree of the page, so the controls on the nested diagram never show up. Here's the sequence:

1. User double-clicks our custom control
2. The nested diagram is obtained from the custom control's parent node Tag property.
3. A new instance of the containing page is created. This page contains an empty diagram upon creation.
4. The nested diagram is passed to the new containing page, and this diagram is substituted for the blank one in the page.

Here's the code for the constructor of our custom Page class:

public MyCustomPage(Diagram d)
{
InitializeComponent();
diagram = d;
} 

"diagram" is the name of the Diagram instance in the page markup. But simply switching out the diagrams doesn't do the trick. The nodes in "d" are there but they don't show up.

Stoyan,

Happily, we came upon the Ruler control, and we simply set the Ruler instance's Document property to the new Diagram instance.

As usual, you guys had already anticipated what was needed.

Thanks!