Bug #5153: Save As... closes all windows associated with a workflow - Kepler - Ecoinformatics Redmine

Actions

Copy link

Bug #5153

open

Save As... closes all windows associated with a workflow

Added by Derik Barseghian over 13 years ago. Updated over 8 years ago.

Status:

New

Priority:

Normal

Assignee:

Derik Barseghian

Category:

interface

Target version:

2.X.Y

Start date:

08/17/2010

Due date:

% Done:

Estimated time:

Bugzilla-Id:

5153

Description

If you're working on a complex workflow, it's not uncommon to have multiple windows open for the one workflow -- windows for different contained composites. When you Save Archive, a new KAR is written, all windows for the workflow are closed, and the new KAR is opened. This process is slow, and also does not open all your windows in the state they were at before save, only the top level window is opened, requiring you navigate through your workflow re-opening everything as you had it.

Actions

Copy link

Updated by Derik Barseghian over 13 years ago

This happens because ExportArchiveAction's refreshFrameAfterSave is set to true by default. The commit log for this feature is:

Author: aschultz
Date: 2009-11-18 12:06:22 -0800 (Wed, 18 Nov 2009)
New Revision: 21670

Modified:
trunk/modules/gui/src/org/kepler/gui/kar/ExportActorArchiveAction.java
trunk/modules/gui/src/org/kepler/gui/kar/ExportArchiveAction.java
Log:
Allow for toggling frame refresh after save until a better solution can be found.

But Aaron, Ben and I can't remember what problem this solution was addressing. I tested changing refreshFrameAfterSave to false by default, and things seem to work fine -- if during Save Archive you change the wf title, that appears, and if you tag, these things roll the revision properly. So offhand I'm not seeing why we need to refresh after save...

Actions

Copy link

Updated by Derik Barseghian over 13 years ago

Save Archive is now called Save As... , and this is still an issue.
The new Save (for kars) doesn't have this problem, so the situation isn't as bad as it was before.

Actions

Copy link

Updated by Aaron Aaron over 13 years ago

Well my first thought was to go build the Nov 11, 2009 Kepler and see what the problem was there. Then see if the problem had been fixed since then. But having some trouble building Nov 11, 2009 Kepler... I'll try just sifting through the code a bit and try to figure it out.

Actions

Copy link