User Details
- User Since
- Aug 1 2016, 12:10 PM (403 w, 4 d)
Aug 2 2016
Unified patch
Images
I've been working on this issue and I found some lines of code that can be changed in order to visualize microscopic images. An example of this kind of images can be downloaded from http://www.insight-journal.org/midas/collection/view/37. It has a resolution of 1nm.
Unified patch
Unified patch
This patch has also the modifications for "T2210"
Unified patch
Unified patch
Be careful, the patch contains also the changes of T3358!
Unified patch
Unified patch
Unified patch
Unified patch
(In reply to comment #2)
It looks like the patch does a lot more than fixing the color issue. Could you
check that please?
Unified patch
Dear Daniel,
Unified patch
I attach you a snapshot and a sample data
I attach you a snapshot and a sample data
Before applying the zoom
After applying the zoom
Unified patch
XRay rendering using Step3.cpp
Extended mitkGPUVolumeMapper3D with vtkImageResample
Dear Mathias,
Dear Mathias,
Unified patch
Modified the default values of top and frontside to be backwards compatible.
I think you can close this issue. I apologize for the confusion.
Best,
Xavi
Unified patch
Sorry Marco, It happens only on the wxMitk version when I press a key used by VTK.
Updated mitkSlicesRotatorMovement.h and mitkSlicesRotatorMovement.cpp. Now it works for any number of cut planes
Sorry, I made a mistake sending the previous one. This is the correct one
Removed observer of time stepper by QmitkStdMultiWidget and moved it to mitk::Interactor::HandleEvent( ). Call mitk::StateMachine::Enable( ) when the interactor is added or removed from GlobaInteraction.
Yes, I'm sure that It solves the problem. Thank you for your effort in solving this issue Ingmar.
Best,
Xavi
Unified patch
Thanks Ingmar for your explanation. You're right, we don't use Undo/Redo. I think your proposed solution is very good.
Just avoid std::memcpy when data is NULL
Dear Tobias,
Hi Michael,
wxWidgets has two versions of SetCursor( ):
- wxWindow::SetCursor( )
- And the global one wxSetCursor( ).
The global one only has an effect on Windows, Mac and GTK+. So we decided to use the wxWindow::SetCursor( ).
The problem arise when using a 3D+T image.
The image has T time steps and XxYxZ dimensions. The image is black except in the middle part of T (from t=2 to t=T-1). In this part, it has a white block in the upper zone that appears and dissapears.
The input data is a 3D+T mitk::PointSet and a 3D+T mitk::Image, both of 4 time steps.
- mitk::PointSet: All time steps empty except time step 3 that contains 1 point at position (300,300,300).
- mitk::Image: origin is (300,300,300) and size (10,10,10).
Unified patch made with the current HEAD SVN version.
wireframe+surface, diffuse and ambient colors, point size
Added an option to display a surface mesh with Surface representation and Wireframe representation at the same time.
Added a property to change the point size of the Points representation
Changed material property to split ColorCoefficient into AmbientCoefficient and DiffuseCoefficient to allow display surfaces like other standard tools