ModelMoverVisual3D Class

ModelMoverVisual3D is a ModelVisual3D object that shows 3 arrows and 3 planes that can be used by user to move a 3D model with dragging the arrows with the mouse.

By default the ModelMoverVisual3D uses shows the arrows in the direction of the standard WPF's axes. But you can change that with using a ModelMoverVisual3D constructor that takes 3 axes as parameter and define your own direction of axes - for example:

Example

You can even define angles that are not aligned with coordinate axes:

Example

When you are using Ab3d.DXEngine to show your scene, it is recommended to show ModelMoverVisual3D in a Viewport3D that is shown over the DXViewportView (as demonstrated in the ModelMoverOverlaySample sample). Note that in this case you cannot use DirectXOverlay as PresentationType because this will prevent showing the Viewport3D overlay.

If you need to use DirectXOverlay as PresentationType or prefer to show ModelMoverVisual3D inside selected object (as demonstrated in the ModelMoverInsideObjectSample sample), then by default the ModelMoverVisual3D will not work because mouse events on UIElement3D objects that are used inside MouseMoverVisual3D will not work.

To make MouseMoverVisual3D work inside Ab3d.DXEngin, the MouseMoverVisual3D also support using Ab3d.Utilities.EventManager3D for processing mouse events.

To make MouseMoverVisual3D work inside DXEngine, the following code changes need to be done:

1) EventManager3D needs to be created and its CustomEventsSourceElement must be set the DXViewportView or a parent Border or some other parent element that has Background property set.

2) When ModelMoverVisual3D is created, we need to call the SubscribeWithEventManager3D method on the created ModelMoverVisual3D and pass the EventManager3D as parameter.

3) To allow user to click on arrows that are inside the selected model, we need to exclude the selected model from being processed by EventManager3D. This can be done with calling RegisterExcludedVisual3D on EventManager3D.

4) Because we called RegisterExcludedVisual3D, we need to call RemoveExcludedVisual3D after the mouse moving is completed.

See the ModelMoverInsideObjectSample sample that comes with Ab3d.DXEngine samples for more information.

Reference