View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004582Slicer4Core: Base Codepublic2018-07-17 21:292018-07-17 21:29
Reporterlassoan Assigned Tojcfr  
PrioritynormalSeverityminorReproducibilitysometimes
Status assignedResolutionopen 
Product VersionSlicer 4.9.0 
Target VersionFixed in Version 
Summary0004582: Make startup complete event triggering order deterministic
Description

Instead of processing startupCompleted events in random order, we should add a method to the module interface similar to qSlicerAbstractCoreModule::initialize, which would be called in the same order as initialize (respecting module dependencies), after application startup is completed.

See background and motivation described in this topic: https://discourse.slicer.org/t/python-unit-test-no-startupcompleted-signal/3494/2

TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2018-07-17 21:29 lassoan New Issue
2018-07-17 21:29 lassoan Status new => assigned
2018-07-17 21:29 lassoan Assigned To => jcfr