Bug #5153

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

Added by Derik Barseghian almost 12 years ago. Updated almost 7 years ago.

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


Estimated time:


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.


#1 Updated by Derik Barseghian almost 12 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

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...

#2 Updated by Derik Barseghian almost 12 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.

#3 Updated by Aaron Aaron over 11 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.

#4 Updated by David Welker over 11 years ago

Pushing further investigation on this enhancement to 2.3. As reported by Aaron, this does not appear to be a current problem.

#5 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 5153

#6 Updated by Daniel Crawl almost 7 years ago

  • Target version changed from 2.5.0 to 2.X.Y

Also available in: Atom PDF