Bug #2990


file|open dialog should open in workflows directory

Added by Matt Jones over 16 years ago. Updated almost 15 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Estimated time:


Kenneth Evans has requested:

Is there an easy way to fix Kepler so the initial directory you get with
File | Open is where your workflows are, rather than where Kepler is.
Just starting Kepler in that directory doesn’t seem to work.

This makes sense to me. I also think the dialog should be saving its state, so that if a user navigates to a new workflow location, the next time it opens it will be in that directory that the user had selected.

Actions #1

Updated by Dan Higgins about 16 years ago

I think we should try to get the initial file dialog to point to the 'demos' directory and then remember the last directory.

Actions #2

Updated by Dan Higgins about 16 years ago

File|Open now initially opens into the $KEPLER/demos directory and remembers where the last location was (until shut-down).

Actions #3

Updated by Christopher Brooks almost 16 years ago

I'm reopening this bug because if the user uses the script
then having File->Open open kepler/demos is odd. Instead we should
open the current directory where the user invoked

The same is probably true for kepler.bat and kepler.exe. We might
want to consider creating a bin directory and placing these scripts
and exes in that directory so that the user can place $KEPLER/bin
in their path.

My rationale on this is that if you think about how a user works on a system,
they are probably working on workflows in their own directory, not
in kepler/demos/.

There is a difference between when a program is invoked from the command
line and when it is invoked from a menu choice.
- If a command is invoked from the command line, then File > Open should
open the current directory
If the command is invoked from a menu choice, then the File -> Open
should ideally open the last directory that was opened (even in a previous
run). Or, having kepler/demos opened is a reasonable work around.

These are just my $0.02. This bug was closed before we had and

Actions #4

Updated by Redmine Admin almost 11 years ago

Original Bugzilla ID was 2990


Also available in: Atom PDF