[Mristudio-users] DTI3DView

[Seongjin]

Dear Kegang,

Thanks for your reply to my query.
I will give it a try.

Thansk again.
-SC

2011/8/1 HUA KEGANG <khua1 at jhu.edu>

>  Hi, SC
>
> The DTI3DView software is developed with Visualization Toolkit(VTK).  The
> operations are consistent with VTK. Here is a snipt from VTK's
> documentation. Hope this can give you some idea.
>
> vtkInteractorStyle <http://classvtkinteractorstyle.html/> implements the
> "joystick" style of interaction. That is, holding down the mouse keys
> generates a stream of events that cause continuous actions (e.g., rotate,
> translate, pan, zoom). (The class vtkInteractorStyleTrackball<http://classvtkinteractorstyletrackball.html/>implements a grab and move style.) The event bindings for this class include
> the following:
>
>    - Keypress j / Keypress t: toggle between joystick (position sensitive)
>    and trackball (motion sensitive) styles. In joystick style, motion occurs
>    continuously as long as a mouse button is pressed. In trackball style,
>    motion occurs when the mouse button is pressed and the mouse pointer moves.
>    - Keypress c / Keypress a: toggle between camera and actor modes. In
>    camera mode, mouse events affect the camera position and focal point. In
>    actor mode, mouse events affect the actor that is under the mouse pointer.
>    - Button 1: rotate the camera around its focal point (if camera mode)
>    or rotate the actor around its origin (if actor mode). The rotation is in
>    the direction defined from the center of the renderer's viewport towards the
>    mouse position. In joystick mode, the magnitude of the rotation is
>    determined by the distance the mouse is from the center of the render
>    window.
>    - Button 2: pan the camera (if camera mode) or translate the actor (if
>    actor mode). In joystick mode, the direction of pan or translation is from
>    the center of the viewport towards the mouse position. In trackball mode,
>    the direction of motion is the direction the mouse moves. (Note: with
>    2-button mice, pan is defined as <Shift>-Button 1.)
>    - Button 3: zoom the camera (if camera mode) or scale the actor (if
>    actor mode). Zoom in/increase scale if the mouse position is in the top half
>    of the viewport; zoom out/decrease scale if the mouse position is in the
>    bottom half. In joystick mode, the amount of zoom is controlled by the
>    distance of the mouse pointer from the horizontal centerline of the window.
>    - Keypress 3: toggle the render window into and out of stereo mode. By
>    default, red-blue stereo pairs are created. Some systems support Crystal
>    Eyes LCD stereo glasses; you have to invoke SetStereoTypeToCrystalEyes() on
>    the rendering window.
>    - Keypress e: exit the application.
>    - Keypress f: fly to the picked point
>    - Keypress p: perform a pick operation. The render window interactor
>    has an internal instance of vtkCellPicker<http://classvtkcellpicker.html/>that it uses to pick.
>    - Keypress r: reset the camera view along the current view direction.
>    Centers the actors and moves the camera so that all actors are visible.
>    - Keypress s: modify the representation of all actors so that they are
>    surfaces.
>    - Keypress u: invoke the user-defined function. Typically, this
>    keypress will bring up an interactor that you can type commands in. Typing u
>    calls UserCallBack() on the vtkRenderWindowInteractor<http://classvtkrenderwindowinteractor.html/>,
>    which invokes a vtkCommand::UserEvent<http://classvtkcommand.html/#a59a8690330ebcb1af6b66b0f3121f8feae177709a43a6bf74fa59806c157bd17f>.
>    In other words, to define a user-defined callback, just add an observer to
>    the vtkCommand::UserEvent<http://classvtkcommand.html/#a59a8690330ebcb1af6b66b0f3121f8feae177709a43a6bf74fa59806c157bd17f>on the
>    vtkRenderWindowInteractor <http://classvtkrenderwindowinteractor.html/>object.
>    - Keypress w: modify the representation of all actors so that they are
>    wireframe.
>
>
> Thanks!
>
> KEGANG(LUKE) HUA
> Department of Radiology
> Johns Hopkins University School of Medicine
> 720 Rutland Ave Traylor217
> Baltimore, MD, 21205
>
>
>  ------------------------------
> Date: Wed, 27 Jul 2011 11:11:27 -0400
> From: choisj70 at gmail.com
> Subject: [Mristudio-users] DTI3DView
> To: mristudio-users at mristudio.org
>
>
> This is a question for the DTI3DView software (for visualizing fibers saved
> in Amira format).
>
> Included manual (in PPT) is not detailed enough to use DTI3DView and
> panning, rotating, and zooming control are somewhat tricky confusing.
>
> It might be better to have detailed manual for DTI3DView.
>
> Anyone who knows about DTI3DView in depth?
>
> Thanks,
> -SC
>
> _______________________________________________ mristudio-users mailing
> list mristudio-users at mristudio.org
> http://lists.mristudio.org/mailman/listinfo/ Unsubscribe, send a blank
> email to: mristudio-users-unsubscribe at mristudio.org
>
> _______________________________________________
> mristudio-users mailing list
> mristudio-users at mristudio.org
> http://lists.mristudio.org/mailman/listinfo/
> Unsubscribe, send a blank email to:
> mristudio-users-unsubscribe at mristudio.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mristudio.org/pipermail/mristudio-users/attachments/20110801/08ea9c82/attachment.html