# Scripted module initialization after application startup is completed

**URL:** <https://discourse.slicer.org/t/scripted-module-initialization-after-application-startup-is-completed/2080>\
**Category:** Development\
**Created:** [February 13, 2018, 4:15pm UTC](https://discourse.slicer.org/t/scripted-module-initialization-after-application-startup-is-completed/2080 "2018-02-13T16:15:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [February 13, 2018, 4:15pm UTC](https://discourse.slicer.org/t/scripted-module-initialization-after-application-startup-is-completed/2080/1 "2018-02-13T16:15:29Z")

</div>

Modules that relied on using a singleshot timer to perform additional initialization steps after Slicer startup is completed, in Slicer-4.9 (recent trunk versions) must switch to use the application’s `startupCompleted()` signal instead. See details in Slicer [migration guide](https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/MigrationGuide/VTK7-Qt4-to-VTK9-Qt5#Slicer_scripted_module_initialization_steps_after_application_startup).