New remote branch pushed: bug-15454-3D-tools-should-report-progress-status
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 2 2016
New remote branch pushed: bug-15448-redesign-fast-marching-3D-tool
New remote branch pushed: bug-15407-ITK-based-2D-region-growing
New remote branch pushed: bug-15339-add-hovering-to-contour-model-interactor
in QmitkSlicesInterpolator, it works for me if I just set:
[f8f7e2]: Merge branch 'bug-15320-weird-livewire-control-points'
Merged commits:
2013-08-08 13:14:53 Sebastian Ordas [9af5d4]
added missing this->
New remote branch pushed: bug-15320-weired-livewire-control-points
[614faf]: Merge branch 'bug-15320-weird-livewire-control-points'
Merged commits:
2013-07-09 14:46:46 Sebastian Ordas [b0fb12]
removed debuging state
New remote branch pushed: bug-15320-weird-livewire-control-points
this bug will be fixed together with 14386
ah ... this is interesting .... let me have a look to one of them
New remote branch pushed: bug-14386-colormaps-and-luts-integration-v3
New remote branch pushed: bug-14386-colormaps-and-luts-integration
New remote branch pushed: bug-14386-colormaps-and-luts-integration-v4
New remote branch pushed: bug-14386-colormaps-and-luts
- short-term solution: use a LUT like in the attachment
A LUT for segmentations
have a look at 14386
A LUT for segmentations
The first step for accomplishing this would be enabling CTK-VTK widgets by default in MITK superbuild. There is a bug tailored to that already: T15401
snapshot showing CTK-VTK widgets for scalar opacity, scalar color, gradient opacity and material properties
snapshot showing CTK-VTK widgets for scalar opacity, scalar color, gradient opacity and material properties
Broken API Sample Code:
(In reply to comment #10)
Broken API Sample Code:
vec3d_units = GetIndexToWorldTransform()->BackTransform(vec3d_mm);New API Sample Code:
vec3d_units =
GetIndexToWorldTransform()->GetInverseTransform()->TransformVector(vec3d_mm);
(In reply to comment #2)
Broken API Sample Code:
warper->SetDeformationField( field );New API Sample Code:
warper->SetDisplacementField( field );
itimage.GoToBegin();
Broken API Sample Code:
template <class TScalarType>
itk::VtkAbstractTransform<TScalarType>::VtkAbstractTransform() :
Superclass(3, 0)
Broken API Sample Code:
I also experienced the same "Multiple symbol definition" link error as in here:
Broken API Sample Code:
this->SetNumberOfOutputs( num );
Broken API Sample Code:
Get_vnl_vector(...
a tough one:
Broken API Sample Code:
itk::Math::RoundHalfIntegerUp( ... );
Broken API Sample Code:
vec3d_units = GetIndexToWorldTransform()->BackTransform(vec3d_mm);
Old API Sample Code:
Set_vnl_vector(...
SetParameters() and SetFixedParameters() are now pure virtual in itk::Transform
Broken API Sample Code:
this->SetNumberOfInputs( num );
not so sure about this one:
Broken API Sample Code:
Some other API change examples:
Broken API Sample Code:
warper->SetDeformationField( field );
New remote branch pushed: bug-11310-change-mouse-cursor-when-tool-is-active
Hello team,
now it works nicely for me :-)
the problem should be around lines 439-452, mitkImageVtkMapper2D.cpp
Hi Caspar,
Hi Caspar,
Hi again, let me just commit the one last error (after changing the names as described in previous posts)
yes, the file exists in that exact location.
In my case, when I apply the proposed patch, the memory indicator decreases immediately. If not, nothing happens (but maybe the memory is indeed being freed)
Thanks for looking into this.
I got the same message on windows XP (MITK SVN)
Hello guys, last night I checked the status of this bug/problem in the current git master, and the issue persists.
hi guys,
Since FIX#2311 (Initialize PointData inOpMove only when non-existent) the problem disappeared, at least for me.