[kepler-dev] [Bug 5637] New: composite window size & position not always saved

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Jul 11 13:57:12 PDT 2012


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5637

             Bug #: 5637
           Summary: composite window size & position not always saved
    Classification: Unclassified
           Product: Kepler
           Version: trunk
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: interface
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: crawl at sdsc.edu
         QAContact: kepler-dev at kepler-project.org


It would be nice if the position and size of a window for a composite actor
were saved. I thought this was done in the past, but I went back as far as
Ptolemy 7.0.1 and Kepler 2.0, and it does not work.

To reproduce:

1. start Ptolemy or Kepler
2. put composite actor on canvas
3. open composite actor
4. resize and move composite actor's window
5. close composite actor's window
6. save model

The size and position of the composite actor's window are not saved in the
model. This configuration is stored in a WindowPropertiesAttribute called
"_windowProperties", and is only stored for the top-level composite actor.

However, I have many existing models that do store the size and position for
composite actor windows. After some testing, I found that before closing the
window in step 5, running File->Save (Ptolemy) or File->Export->XML (Kepler) in
the composite actor window does store the size and position for the composite.

To fix this would be to store the size and position for all open composite
actor windows regardless if File->Save is used.

Note that in Kepler, File->Save saves the model as a KAR, and this also does
not save window size and position, but this is a different problem - see bug
5188.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.


More information about the Kepler-dev mailing list