Feature #814

qview does not take a -pref command line argument

Added by Stuart Sides over 5 years ago. Updated 12 days ago.

Target version:

Minor - Impacted Isis Applications include all QIsisApplications.

Software Version:
Test Reviewer:


qview does not accept a command line argument to allow the user to set their preferences. This causes a problem when spiceinit was run using a special preference file and a kernel location set using one of the Isis environment variables e.g., "lro", "mro". qview can not find the kernel file so it fails to create a camera therefore the user sees no lat/lon


#1 Updated by Tammy Becker over 5 years ago

Steven helped with estimated hours. There is a 'quick' fix that will take less than 20 hours and a 'real' fix that will take greater than 20 hours.

#2 Updated by Anonymous over 4 years ago

  • Target version deleted (150)

#4 Updated by Stuart Sides about 2 months ago

  • Assignee set to Adam Goins

#5 Updated by Stuart Sides about 2 months ago

  • Status changed from Acknowledged to Assigned

#6 Updated by Adam Goins about 2 months ago

  • Status changed from Assigned to In Progress

#7 Updated by Adam Goins about 1 month ago

  • Status changed from In Progress to Resolved
  • Impact updated (diff)

QView (and all QIsisApplications) can now receive a custom preference file by specifying the file in command line as follows:

qview -pref my_file

#8 Updated by Stuart Sides about 1 month ago

  • Target version set to 3.5.2 (2017-01-31 Jan)

#9 Updated by Stuart Sides 24 days ago

  • Status changed from Resolved to Closed

#10 Updated by Adam Goins 12 days ago

In work project there's an IsisPreferencesTemp file that can be used to test against.

There's a DataDirectory group at the bottom that can be modified to change the path in which the mission data points to.
By default it's $ISIS3DATA/[mission], however this can be changed to point to wherever the user has that mission data stored.

Also available in: Atom PDF