Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organizationName) then that file is used instead.

By default, (applicationName)=Slicer and (organizationName)=NA-MIC and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organization) then that file is used instead.

By default, (applicationName)=Slicer and (organization)=NA-MIC (or the organization URL, depending on the operating system), and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

This fixes Slicer#4966. The only remaining (known) limitation is that the DICOM database is still stored with an absolute path, because the DICOM database is not yet relocatable (Slicer#4722).

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organization) then that file is used instead.

By default, (applicationName)=Slicer and (organization)=NA-MIC (or the organization URL, depending on the operating system), and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

Fixes Slicer#4966
Fixes Slicer#4722

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organization) then that file is used instead.

By default, (applicationName)=Slicer and (organization)=NA-MIC (or the organization URL, depending on the operating system), and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

Fixes Slicer#4966
Fixes Slicer#4722

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organization) then that file is used instead.

By default, (applicationName)=Slicer and (organization)=NA-MIC (or the organization URL, depending on the operating system), and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

Fixes Slicer#4966
Fixes Slicer#4722

Slicer install tree was portable but not fully self-contained, as settings and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled by default) that makes Slicer store all settings and extensions in the application home folder, within (organizationName) subfolder (as QSettings default constructor saves settings file into (organizationName) subfolder by default), making the application fully portable.

To still allow having settings that are common to all installed application versions for a user (e.g., DICOM database folder, confirmation popup suppressions, ...), the common non-revision-specific is still stored in the user profile directory by default. However, if the user places an (applicationName).ini file in the application home folder/(organization) then that file is used instead.

By default, (applicationName)=Slicer and (organization)=NA-MIC (or the organization URL, depending on the operating system), and therefore the .ini files are: (applicationHome)/NA-MIC/Slicer.ini and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths that are child folders of (applicationHome) are stored as relative paths. All relative paths remain valid when the application is moved to a different location.

Fixes Slicer#4966
Fixes Slicer#4722

Slicer install tree was portable but not fully self-contained, as settings
and extensions were stored in the user profile folder.

Added a new option Slicer_STORE_SETTINGS_IN_APPLICATION_HOME_DIR (enabled
by default) that makes Slicer store all settings and extensions in the
application home folder, within (organizationName) subfolder (as QSettings
default constructor saves settings file into (organizationName) subfolder
by default), making the application fully portable.

To still allow having settings that are common to all installed application
versions for a user (e.g., DICOM database folder, confirmation popup
suppressions, ...), the common non-revision-specific is still stored
in the user profile directory by default. However, if the user places
an (applicationName).ini file in the application home folder/(organization)
then that file is used instead.

By default, (applicationName)=Slicer and (organization)=NA-MIC (or the
organization URL, depending on the operating system), and therefore
the .ini files are: (applicationHome)/NA-MIC/Slicer.ini
and (applicationHome)/NA-MIC/Slicer-(revision).ini; and extensions are
stored in (applicationHome)/NA-MIC/Extensions-(revision).

Also updated all path reading/writing in settings files so that paths
that are child folders of (applicationHome) are stored as relative paths.
All relative paths remain valid when the application is moved to a
different location.

Fixes Slicer#4966
Fixes Slicer#4722

----
List of CTKAPPLauncher changes:

$ git shortlog v0.1.27..v0.1.28 --no-merges
Andras Lasso (1):
      ENH: Allow user settings file to be in <APPLAUNCHER_DIR> (PR-114)

James Butler (1):
      COMP: Fix deprecation warning C4996

Jean-Christophe Fillion-Robin (3):
      Begin post-v0.1.27 development [ci skip]
      Fix deployment updating API key used for release upload
      CTKAppLauncher v0.1.28

Steve Pieper (2):
      BUG: fix crash calculating environment keys
      STYLE: use clearer syntax for constructor

----
List of CTKAppLauncherLib changes:

$ git shortlog 692164..a3100a4 --no-merges
Andras Lasso (1):
      ENH: Allow user settings file to be in <APPLAUNCHER_DIR> (PR-114)

Jean-Christophe Fillion-Robin (2):
      Fix deployment updating API key used for release upload
      CTKAppLauncher v0.1.28