User Details
- User Since
- Aug 1 2016, 12:10 PM (441 w, 3 h)
- Roles
- Disabled
Aug 2 2016
fixed...:)
BTW: Our system is windows xp, 32bit
works now
Since I'm not sure about the desired behaviour I don't feel confident to decide this.
A preliminary test by declaring the supposably obsolete methods:
The documentation is already written.
As michale commented, it works with the described option on xins computer now. Since there's no machine left with the described malfunction, the bug can be closed.
The Problem seems to be a missing CMake Option in VTK. Everyone, who didi not compile VTK himself, should do so using the description on
[SVN revision 22452]
ADD (#3120): Packed all needle finder files into one module and began with code cleaning
[SVN revision 22455]
COMP (#3120): removed typename
[SVN revision 22454]
COMP (#3120): removed braces
[SVN revision 22448]
ADD (#3120): Created a new bundle to use the needle finder alg
[SVN revision 21049]
ADD (#3067): Added the feature of Intensity Profile Generation along a planar line. Results will be shown in the histogram widget. bug not resolved yet, but basic operativeness provided.
Tried to add a new state to the statemachine to reset the mousepointer.
Added a state in statemachine xml. Called from stdmultiwidget. That did not solve the problem.
Tried to add a new state to the statemachine to reset the mousepointer.
Fixed by:
[SVN revision 20351]
FIX (#1895): Replaced the "Toggle Visibilty Workaround" by a real estimation of
the chekstate
When doing the workflow described in comment 3 but selecting the surface between the steps instead of turning visibility on and off, the same behaviour is observed. Suspicion: There is a orphan pointer which is held by some gui class and therefore a corrupted state of the property list is created by the respecting classes.
The problem occured, when testing the Organ Segmentation bundle. As stated, the crashes occured only occasinally and the app threw an exception.
Fixed at revision 19953
I'm at it
Began to wirte test, but I am not sure about the desired behaviour of the class meitk::Pixeltype. Therefore the test would fail. It is excluded from compilation.
Opened T3255 to clarify the correct behaviour of the class
[SVN revision 21132]
ADD (#2660): Added the mitkPixelType test... is excluded from compilation see bug for details
Began to wirte test, but I am not sure about the desired behaviour of the class meitk::Pixeltype. Therefore the test would fail. It is excluded from compilation.
Region Growing is almost unusable slow...
An example dataset is:
G:\home\hartmanp\I0000006.vol
made a preliminarsy fix of the huge mess in levelwindow.... had to adapt the test too.... many problems, no light at the end of the tunnel...
prelim changes
change request for core mod
reverted recent changes due to failning unit test
[SVN revision 21209]
FIX (#2191): Made LevelWindow consitent by removing unnecessary member variables
due to excessive problems with the wiki template thing, we added this textfile as a change request
[SVN revision 20351]
FIX (#1895): Replaced the "Toggle Visibilty Workaround" by a real estimation of the chekstate
partybug
Lines have to be added at QmitkMainTemplate.ui.h: line 1477, line 750, line 956 for proper read / write of a zoom factor property. cmp to "Use gradient Background" property