Ticket #2625 (assigned)

Opened 10 years ago

Last modified 5 years ago

Save Directory - Browse button should default to Last navigated save directrory

Reported by: Nick Draper Owned by: Martyn Gigg
Priority: major Milestone: Backlog
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester:

Description (last modified by Nick Draper) (diff)

From Dean Whittaker (d.whittaker@…):

I suppose this is more a feature request. When saving a file (in my case an "include" file for detectors to turn into a map file) it always jumps to some default directory instead of the directory I was last in - obviously if I last saved a file in a directory, it is likely the next file I save will also go there.. Also, it can't follow shortcuts. Instead it tries to save over the top of them. Surely I should double click a shortcut and it'll take me to the relevant folder, not assume that I want to save my file as "merlin.lnk" (for example).

From Nick Draper:

Thanks for the feedback, I'm sure we can improve the automatically selected directory in when using the browse button. Navigating through shortcuts may be more of a challenge as that is very much down to the underlying tools we are using to create the user interface, and I suspect we will get different behaviour on different operating systems. We will take a look though, I've created a work ticket so a member of the development team to look into these issues for the next release.

In the mean time you can change the Default Save Directory (look under File->Manage Directories), that is the directory the browse button is defaulting to.

Suggestion:

We should default to the last navigated save directory first with the default save as a backup. Don't save the last navigated directory between runs of Mantidplot.

Change History

comment:1 Changed 10 years ago by Nick Draper

  • Description modified (diff)

comment:2 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 28 to Iteration 29

Bulk move of tickets at the end of iteration 28

comment:3 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 29 to Iteration 30

"New" tickets moved at the code freeze of iteration 29

comment:4 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:5 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:6 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:7 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:8 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to milestone 2.4

comment:9 Changed 8 years ago by Martyn Gigg

  • Milestone changed from Release 2.4 to Release 2.5

comment:10 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.5 to Release 2.6

Moved to r2.6 at the end of r2.5

comment:11 Changed 7 years ago by Martyn Gigg

  • Milestone changed from Release 2.6 to Release 2.7

Batch move to 2.7

comment:12 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.7 to Backlog

comment:13 Changed 7 years ago by Nick Draper

  • Component changed from Mantid to Framework

comment:14 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:15 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3472

Note: See TracTickets for help on using tickets.