You can start Insight with a positional argument pointing to the container xml (e.g. container.xml for the "normal" Insight, containerImport.xml for the Importer). In the OSX build this argument is set by OMERO.insight.cfg:
[ArgOptions]
container.xml
Without this PR the container xml has to be in the config directory within the bundle. With this PR you can point to any location. If the argument contains at least one path character it is assumed it specifies a file outside the bundle, if it doesn't (i.e. it's only a file name) it's assumed that it specifies a file within config directory of the bundle.
The PR also removes the code to enable the DebugRepaintManager, as it's actually not used any more.
Fixes https://github.com/ome/omero-insight/issues/363 .
You can start Insight with a positional argument pointing to the container xml (e.g. container.xml for the "normal" Insight, containerImport.xml for the Importer). In the OSX build this argument is set by OMERO.insight.cfg:
Without this PR the container xml has to be in the config directory within the bundle. With this PR you can point to any location. If the argument contains at least one path character it is assumed it specifies a file outside the bundle, if it doesn't (i.e. it's only a file name) it's assumed that it specifies a file within config directory of the bundle.
The PR also removes the code to enable the DebugRepaintManager, as it's actually not used any more.