View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001655Slicer4Core: Base Codepublic2012-01-19 05:152012-12-20 17:22
Reporterlassoan Assigned Tojcfr  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product VersionSlicer 4.0.1 
Target VersionSlicer 4.3.0Fixed in VersionSlicer 4.2.2-1 
Summary0001655: Allow different module paths definition for each Slicer instance
Description

There is one single Slicer.ini file on a computer, which stores the additional module paths. The problem is that multiple versions of Slicer can be installed at the same time (different revisions, debug/release, etc.) and each module is compatible with only one specific Slicer version.

If the user installs Slicer 4.1.2 then downloads a few extensions for this version then downloads Slicer 4.2.3 and attempts to start it Slicer may crash.
If the developer builds and tests a module in debug mode then wants to test it in release mode (without deleting the debug mode module) Slicer may crash.

There are some other settings that should be possible to set for a single Slicer instance only (such as disabling CLI for debugging). Some settings are OK to be the same for the whole system (such as favorite folders). The solution could be to have a global Slicer.ini file with the common system-wide settings and separate ini files (or separate sections in the global ini file) for each Slicer instance. An instance could be best defined by its path.

TagsNo tags attached.

Relationships

related to 0001958 closedjcfr extension from one version shows up in other version 
related to 0001969 closedpieper can't import dicom images 

Activities

finetjul

finetjul

2012-02-22 10:40

administrator   ~0003690

as a side fix (or a complimentary fix), maybe the settings file path could be passed via the launcher command line.
pinter

pinter

2012-12-08 12:28

developer   ~0007479

Has this issue been solved by the fix applied for 1958 and the related tickets?
jcfr

jcfr

2012-12-09 07:00

administrator   ~0007481

It should be fixed.

For reference:
trunk: http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21482
4.2 branch: http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21489
lassoan

lassoan

2012-12-20 17:22

developer   ~0007564

Tested on the latest Slicer release (4.2.2-1 Win64) and it worked well.

For developers on Windows it would be useful to make an additional enhancement: slightly change the version ID for debug-mode builds, such as Slicer-21513-D.ini (instead of Slicer-21513.ini). It would allow running debug and release builds of the same Slicer revision on the same computer without messing around with ini files.

Issue History

Date Modified Username Field Change
2012-01-19 05:15 lassoan New Issue
2012-01-19 05:15 lassoan Status new => assigned
2012-01-19 05:15 lassoan Assigned To => finetjul
2012-01-19 05:33 finetjul Assigned To finetjul => jcfr
2012-02-22 10:40 finetjul Note Added: 0003690
2012-06-04 06:01 jcfr Target Version => Slicer 4.2.0 - Sept 1st 2012
2012-06-04 06:02 jcfr Relationship added related to 0001958
2012-08-20 10:02 jcfr Target Version Slicer 4.2.0 - Feature freeze Sept 1st 2012 => Slicer 4.2.5
2012-08-21 09:39 jcfr Target Version Slicer 4.2.5 => Slicer 4.3.0
2012-08-22 05:17 pieper Relationship added related to 0001969
2012-12-08 12:28 pinter Note Added: 0007479
2012-12-09 07:00 jcfr Note Added: 0007481
2012-12-09 07:00 jcfr Status assigned => resolved
2012-12-09 07:00 jcfr Fixed in Version => Slicer 4.2.2
2012-12-09 07:00 jcfr Resolution open => fixed
2012-12-20 17:22 lassoan Note Added: 0007564
2012-12-20 17:22 lassoan Status resolved => closed