Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default "load data" directory to the last one used (Trac #230) #378

Closed
ajj opened this issue Mar 30, 2019 · 9 comments
Closed

Default "load data" directory to the last one used (Trac #230) #378

ajj opened this issue Mar 30, 2019 · 9 comments
Labels
Enhancement Feature requests and/or general improvements Minor Small job

Comments

@ajj
Copy link
Member

ajj commented Mar 30, 2019

Migrated from http://trac.sasview.org/ticket/230

{
    "status": "closed",
    "changetime": "2017-04-06T09:51:58",
    "_ts": "2017-04-06 09:51:58.562443+00:00",
    "description": "",
    "reporter": "ajj",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView GUI Enhancements",
    "time": "2014-04-03T10:10:37",
    "component": "SasView",
    "summary": "Default \"load data\" directory to the last one used",
    "priority": "minor",
    "keywords": "",
    "milestone": "SasView Next Release +1",
    "owner": "",
    "type": "enhancement"
}
@ajj ajj added this to the SasView Next Release +1 milestone Mar 30, 2019
@ajj ajj added Enhancement Feature requests and/or general improvements Incomplete Migration Minor Small job and removed Incomplete Migration labels Mar 30, 2019
@butlerpd
Copy link
Member

Trac update at 2014/04/05 20:55:41:

  • butler commented:

This is supposed to work and code looks like it should work but it doesn't always do so.

  • butler changed milestone from "SasView 3.0.0" to "SasView Next Release +1"

@ajj
Copy link
Member Author

ajj commented Mar 30, 2019

Trac update at 2015/01/14 12:37:23: ajj changed workpackage from "" to "SasView Bug Fixing"

@butlerpd
Copy link
Member

Trac update at 2015/02/01 23:05:50: butler changed milestone from "SasView Next Release +1" to "SasView 3.1"

@butlerpd
Copy link
Member

Trac update at 2015/03/10 16:54:54:

  • butler commented:

We need to agree on what we want as the new interface for this. Probably a real preferences window that lets one enter values for the items set in the configuration file (at least those we will allow the user to change). That however will be a major undertaking so probably not for this release. Hence moving from 3.1 to next + 1

  • butler changed milestone from "SasView 3.1" to "SasView Next Release +1"

@butlerpd
Copy link
Member

Trac update at 2015/03/22 22:54:28:

  • butler changed type from "defect" to "enhancement"
  • butler changed workpackage from "SasView Bug Fixing" to "SasView GUI Enhancements"

@ajj
Copy link
Member Author

ajj commented Mar 30, 2019

Trac update at 2017/04/04 21:56:47: ajj commented:

This seems to be working? Is it fixed?

@sasview-bot
Copy link

Trac update at 2017/04/04 22:25:38: krzywon commented:

I tested v4.1.0 release using Win10 and I agree with Andrew, this looks like it's working.

@butlerpd
Copy link
Member

Trac update at 2017/04/05 21:21:19: butler commented:

Would be very happy to get a consensus and close this but absolutely nothing has changed since the ticket was first written. The problem is one of choosing the expected behavior. currently (as it has for a long time) the last directory from which a file was loaded is the default directory for the next load. However, it does not persist from session to session unless the new default directory is saved by clicking View ->Startup Settings and choosing "current View"

If it should persist without that then we should change that menu and also the behavior. I am all in favor of that but since the ticket was raised by someone else....

Ultimately (mainly in new GUI?) we should probably replace that clunky mechanism with a proper setting page.

@ajj
Copy link
Member Author

ajj commented Mar 30, 2019

Trac update at 2017/04/06 09:51:58:

  • ajj changed resolution from "" to "fixed"
  • ajj changed status from "new" to "closed"

@ajj ajj closed this as completed Mar 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Feature requests and/or general improvements Minor Small job
Projects
None yet
Development

No branches or pull requests

3 participants