[SVN revision 28970]
FIX (#6544): added constraints that will prevent false movements such as spinning and flipping of the surface;

[SVN revision 29391]
FIX (#6502): removed unfinished kalman filter from data processing;

[SVN revision 28784]
FIX (#6502): created initial non-functional design of a kalman filter;

[SVN revision 28690]
FIX (#6467): added first transversal scrolling by using an additional IR source;

[SVN revision 28923]
FIX (#6467): changed tracking behavior from headtracking and transversal scrolling, thus only one IR source is needed for each interaction;

[SVN revision 28823]
FIX (#6467): changed scrolling behavior from mapping to relative movement with threshold;

[SVN revision 28655]
FIX (#6402): fixed variable names;

[SVN revision 28661]
FIX (#6401): fixed path for wiimote model;

[SVN revision 28473]
FIX (#6401): using quaternion for the 3D representation;

[SVN revision 28589]
FIX (#6402): added rotation from camera view; separated from interaction relative to object by different modes;

[SVN revision 28663]
FIX (#6402): added mode changer for surface interaction;

Prototyp GUI and Threading

This fix changes the driver, which should not be done due the fact that a newer version cannot simply replace the old one.

unclean fix for dependency problem to the wiimote module

This is actually the intented behaviour. You need to specifically activate the additional flags when the bundle is needed and the driver/configurations (which are required) are installed. Otherwise the classes will cause compile errors.

[SVN revision 25385]
FIX (#5037): reversed changes in interface IPreferencePage and childs;root node now flushes all preferences

(In reply to comment #5)

Sorry for reopening, but I think the solution is over-engineered.

Instead of introducing another method in the interface IPreferencePage
(FlushPreferences()), I think just calling flush on the root node in
QmitkPreferencesDialog::OnApplyButtonClicked is enough. This should flush all
the child nodes too:

void QmitkPreferencesDialog::OnApplyButtonClicked( bool /*triggered*/ )
{

...

berry::IPreferencesService::Pointer prefService =

m_PreferencesService.Lock();

if (prefService)
{
  prefService->GetSystemPreferences()->Flush();
}

this->done(QDialog::Accepted);

}

[SVN revision 25356]
COMP (#5037): Some child classes did not implement the new Flush() method

Core UI changes for the flushing preferences directly

[SVN revision 25358]
COMP (#5037): namespaces were used incorrectly

Core UI changes for the flushing preferences directly

[SVN revision 25353]
FIX (#5037): Flushing the preferences is now done in QmitkPreferencesDialog#OnApplyButtonClicked

[SVN revision 25496]
COMP (#4965): deactivated module as well

[SVN revision 25527]
COMP (#4965): fixed linker problem by manually adding a linker language

[SVN revision 25544]
FIX (#4965): space navigator bundle removed from exclude list and fixed space navigator driver

[SVN revision 27341]
FIX (#4965): added comment about error when using /MP

[SVN revision 25545]
COMP (#4965): only windows compatible - bundles and module will only be built in windows

[SVN revision 25525]
FIX (#4965): spacenavigator on default excluded; module classes are loaded individually depending on flags

[SVN revision 25533]
COMP (#4965): used correct syntax for set_target_properties

[SVN revision 25546]
COMP (#4965): fixed driver with additional ifdef

[SVN revision 25474]
COMP (#4965): removed unused symbols

core changes for the input device integration

[SVN revision 25486]
COMP (#4965): added TDxInput.tlh to solve problem with progid

[SVN revision 25473]
COMP (#4965): removed ascii symbol in scope of eventmapper method

[SVN revision 25492]
COMP (#4965): removed TDxInput.tlh,because does not work and deactivated both bundles

[SVN revision 25472]
FIX (#4965): input devices reimplemented with extension points

[SVN revision 25477]
COMP (#4965): fixed problem with const iterator and the method erase from vector

In an earlier version of the MITK with QT3, code was developed to integrate a 3D Connexion mouse (modelname: Space Navigator). This input device should provide a possibility to navigate in a 3D space without using keyboard and a normal mouse simultaneously. Unfortunately the design of the integration wasn't modular. Therefore it was mandatory to design a new pattern, which allows on the one hand to easily integrate new input devices and on the other hand to be as modular as possible.

core changes for the input device integration

(In reply to comment #1)

(I'm resetting the core modification flag because no wiki page is linked and no
references to core modifications are made in the description)

In addition there should be a test to check the boundaries against the control points, so that other test cases won't fail because of the same problem.

I looked into mitkPlanarCrossTest.cpp, method TestPlanarCrossPlacementConstrained(). And in this case the control point would be ok. But the problem is, there are additional constraints (we refered to them as "boundaries"), which are applied in mitkPlanarCross.cpp.

[SVN revision 27027]
FIX (#3281): fixed problem with case sensitivity and activated extension point context menu

[SVN revision 27029]
FIX (#3281): removed unused variable

[SVN revision 27024]
FIX (#3281): deactivated postprocessing class and activated extension point functionality

[SVN revision 27014]
FIX (#3281): added CreatePolygonModelAction with Extension Points and changed include order

[SVN revision 27020]
FIX (#3281): added StatisticsAction with Extension Points and changed include order

[SVN revision 26631]
FIX (#3281): restored postprocessing functionality as long as the context menu is not fully integrated through extension points

[SVN revision 27026]
COMP (#3281): reactivated postprocessing and deactivated extension points functionality

[SVN revision 26819]
FIX (#3281): added Thresholdaction with Extension Points and change include order

As proposed the nodedescriptors are now provided through extension points. The class QmitkSegmentationPostProcessing was splitted in several classes to be accessible separately. The functions are now available without the segmentation view being open and also work as they did before.

[SVN revision 26623]
COMP (#3281): changed include order in contextmenuaction.h and autocropaction

[SVN revision 26443]
COMP (#3281): removed unused variables and fixed case sensitive include in manifest.cpp

screenshot of the problem

context menu implemented with extension points

[SVN revision 26453]
COMP (#3281): changed include order, poco classes at the very top

screenshot of the problem

[SVN revision 26444]
COMP (#3281): moved critical include to the top of the class and changed include order in manifest.cpp

[SVN revision 26617]
FIX (#3281): adding autocrop action only with extension point contextmenu

[SVN revision 26442]
FIX (#3281): used extension points from BlueBerry to integrate context menu

[SVN revision 26460]
COMP (#3281): forced poco include before any other include

[SVN revision 26461]
COMP (#3281): reverted manifest.cpp to remove build warnings in linux

This patch includes all changes that will be needed to change the problem of the context menu being only available when the segmentation view is open.

[SVN revision 26457]
COMP (#3281): changed include order

[SVN revision 26466]
COMP (#3281): reverted all changes because of poco error

I was trying to setup my MITK (http://mbits.inet.dkfz-heidelberg.de/mbiwiki/VisualStudio) and followed the link in the general instructions (http://mbits/doxygen/BuildInstructionsPage.html). I had one problem so far:

[SVN revision 28728]
FIX (#1543): added fix for higher resolution acceleration values (x,y,z); removed tabs, formatting changed slightly;

[SVN revision 28474]
FIX (#1543): added code to record raw data of wiimote;

[SVN revision 28198]
FIX (#1543): fixed problem with release mode; motion plus now works properly

[SVN revision 28391]
FIX (#1543): added dynamic orientation with data from gyroscopes; added reset function;

[SVN revision 28785]
FIX (#1543): removed required lib dependencies because there are problems with the current WDK (7.1.0) and VC8; added notice and referred to mitk homepage;

[SVN revision 27672]
FIX (#1543): fixed warning by using class instead of struct for EventMapperAddOn.h

[SVN revision 28187]
FIX (#1543): added still buggy translation and simple rotation through acceleration data

[SVN revision 27923]
FIX (#1543): added new statemachinepattern to restrict movement to button push; changed old statemachinepattern name to "WiiMoteHeadtracking"; implemented initial processing of the data in WiiMoteInteractor

[SVN revision 27812]
FIX (#1543): added event for all incoming data, wiimote model for 3D view, first version of interactor and a simple statemachine pattern

[SVN revision 28164]
FIX (#1543): added acceleration values to WiiMoteAllDataEvent;

[SVN revision 27686]
FIX (#1543): added mechanism and gui elements to distinguish headtracking and surface interaction modus

[SVN revision 27931]
FIX (#1543): replaced ForceImmediateUpdate with RequestUpdate to solve problem with delay; added orientation and update age to WiiMoteAllDataEvent

[SVN revision 28041]
FIX (#1543): added fix for orientation parameter and added 2 additional (roll,pitch)

[SVN revision 27595]
FIX (#1543): integrated Motion Plus

[SVN revision 26662]
COMP (#1543): added return value to RegisterInputDevice method

[SVN revision 26808]
FIX (#1543): added multiple wiimote support to thread for testing purpose

[SVN revision 27403]
FIX (#1543): re-enabled WiiMoteActivator class

[SVN revision 27591]
FIX (#1543): Core changes for VR Headtracking

For the WiiYourself library to work there are dependencies necessary. This outline will describe an attempt to integrate them properly into MITK.

[SVN revision 26909]
FIX (#1543): separated wiimote and spacenavigator

[SVN revision 26859]
FIX (#1543): added first version of multiIRevent for processing data coming from multiple wiimotes

[SVN revision 26658]
FIX (#1543): added calibration for sensitivity and created distinguishable event classes