Page MenuHomePhabricator

Interaction failure with installed MITK application from mitk.org
Closed, DuplicatePublic

Description

After installing the automatically (nightly) built MITK executable (mitk.org/download), there are warning regarding the interaction after loading pic3d.pic (see below).
Warnings do not use mbilog, but ugly output window.

--> In consequence, e.g. the interaction on 2D windows does not work.

Tested with setup routine:
MITK-0.13.1_r18193-win32.exe 16-Jul-2009 01:09 17M

StateMachine.xml was installed properly with the setup routine.

WARNING: In ..\..\..\mitkOpenSourceSVN\Core\Code\Interactions\mitkStateMachineFactory.cpp, line 89 Start state not found for state-machine "navigation".
WARNING: In ..\..\..\mitkOpenSourceSVN\Core\Code\Interactions\mitkStateMachineFactory.cpp, line 89 Start state not found for state-machine "slices-rotator".
WARNING: In ..\..\..\mitkOpenSourceSVN\Core\Code\Interactions\mitkStateMachineFactory.cpp, line 89 Start state not found for state-machine "moveNzoom".
WARNING: In ..\..\..\mitkOpenSourceSVN\Core\Code\Interactions\mitkStateMachineFactory.cpp, line 89 Start state not found for state-machine "navigation".

Event Timeline

Does the output say anything about MainApp correctly finding and loading StateMachine.xml? Perhaps the file is not in a place that is searched by mitk::StandardFileLocations?

changerequest2279

After some investigation by Michi Mueller, we found out:

  • Error occurs, because statemachine.xml is not found
  • CPack installation creates windows startmenu shortcuts that have a 'working directory entry' pointing to the base installation directory, but not to the ./bin subdirectory where all files are located

propose to add the ./bin subdirectory in the default search policy of mitk::StandardFileLocations (see attached core change request).

(In reply to comment #3)

propose to add the ./bin subdirectory in the default search policy of
mitk::StandardFileLocations (see attached core change request).

Different solution proposal: T2413 will fix this, I need to know though where to put some general Qt-dependent init call in the cherry apps. Michi? It used to be in QmitkMainTemplate ...

Have a look in QmitkWorkbenchWindowAdvisor::PostWindowCreate(), mitk\CoreUI\Bundles\org.mitk.gui.qt.application\src\internal
Theres a nice class from Daniel M, called "QmitkWorkbenchWindowAdvisorHelperHack". This is the best place to put dirty hacks.

Is now a duplicate of #2413: Controlled initialization of EventMapper and StateMachines. ->Closed.

Hi, your bug is resolved, can you please remove the needs_core_modification request (set it to - or nothing)? Otherwise it clutters the list of open requests which is not filterable by status.

This will help granting the flag for open bugs much faster ;)