Ticket #2901 (assigned)
Default "defaultsave.directory" on Mac is inaccessable
| Reported by: | Michael Whitty | Owned by: | Anyone |
|---|---|---|---|
| Priority: | major | Milestone: | Backlog |
| Component: | Framework | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: |
Description
When installing MantidPlot on a Mac, the default defaultsave directory is the location of the executable, as it is in Windows and Linux.
However, this location is not accessible, which will present the user with errors if they try and save something (as I think most of our users will want to do).
Could we perhaps choose a saner place? Ie, create a directory in the users /home or whatever the Mac-y equiv is.
This may also be the case on RPM builds.
Change History
comment:2 Changed 9 years ago by Nick Draper
- Status changed from new to assigned
- Owner set to Anyone
comment:3 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:4 Changed 9 years ago by Mathieu Doucet
- Owner changed from Anyone to Mathieu Doucet
- Status changed from assigned to accepted
comment:6 Changed 9 years ago by Mathieu Doucet
- Status changed from accepted to verify
- Resolution set to fixed
To test:
- Remove the defaultsave.directory entry in your Mantid.user.properties file.
- Start MantidPlot and start the "Manage User Directories" dialog in the File menu.
- The Default Save Directory should be your home directory.
Second test:
- Click the Browse to Directory button next to the Default Save Directory field.
- The Select New Default Save Directory dialog should start in your home directory.
- Click Cancel, then erase the path in the Default Save Directory field and leave it empty.
- Click the Browse button again.
- It should now be in your last visited directory (or some absurd default such as the release directory)
comment:7 Changed 9 years ago by Mathieu Doucet
- Status changed from verify to reopened
- Resolution fixed deleted
comment:10 Changed 9 years ago by Mathieu Doucet
In [14943]:
comment:11 Changed 9 years ago by Russell Taylor
For information, #404 was the original ticket under which the conversion of relative paths to absolute ones was introduced.
comment:12 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:13 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:14 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:15 Changed 8 years ago by Mathieu Doucet
- Owner changed from Mathieu Doucet to Anyone
- Status changed from reopened to assigned
comment:16 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:17 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:18 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.5 to Release 2.6
comment:21 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at the code freeze for R2.6
comment:22 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:23 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 3748
"New" tickets moved at the code freeze of iteration 29