Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring Slicer_DEFAULT_HOME_MODULE with "DICOM" fails to bring up Dicom module on startup #42

Open
HarryDC opened this issue Aug 24, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@HarryDC
Copy link
Contributor

HarryDC commented Aug 24, 2022

when implementing set(Slicer_DEFAULT_HOME_MODULE "DICOM") in the toplevel CMAKE file the application fails to enter the DICOM module on startup, conversely if the module is set in DefaultSettings.ini the module correctly comes up.

@HarryDC
Copy link
Contributor Author

HarryDC commented Aug 24, 2022

qSlicerModulesMenu::setCurrentModule gets called from the init function of qSlicerSettingsModulesPanel, this seems to be fairly early during the startup, the call with the #define that gets populated from the CMAKE variable, fails and returns a nullptr for an action. But when it's called later with the value that's read from the .ini file i think in qSlicerMainWindow the call succeeds and the dicom module is selected. The second call happens a lot later it looks like it's triggered by postInitializeApplication in qSlicerApplicationHelper

@HarryDC HarryDC added the bug Something isn't working label Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant