Uploaded image for project: 'GMAT'
  1. GMAT
  2. GMT-6498

DynamicDataDisplay window is not closed when all other windows are closed

    Details

      Description

      The DynamicDataDisplay window does not close when using the Close/Close All buttons in the GMAT GUI and does not close with other windows when a new script is loaded. This is most likely due to this window not being the same type as the other windows (plots, 3D visualizations, etc.).

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jraymond Joshua Raymond added a comment -

            On Windows 10, when a mission is rerun, the DynamicDataDisplay window will cycle between closing and opening. In other words, if the window is currently visible and then the mission is run, the window is closed for that run. Running again will open the window. If the user closes the DynamicDataDisplay window before rerunning, the window will correctly open for the new run.

            Show
            jraymond Joshua Raymond added a comment - On Windows 10, when a mission is rerun, the DynamicDataDisplay window will cycle between closing and opening. In other words, if the window is currently visible and then the mission is run, the window is closed for that run. Running again will open the window. If the user closes the DynamicDataDisplay window before rerunning, the window will correctly open for the new run.
            Hide
            djcinsb Darrel Conway added a comment -

            Your turn. I added a generic output type for this. We'll want Tetyana to watch it closely in case there are side effects.

            Show
            djcinsb Darrel Conway added a comment - Your turn. I added a generic output type for this. We'll want Tetyana to watch it closely in case there are side effects.
            Hide
            jraymond Joshua Raymond added a comment -

            The DynamicDataDisplay window does not maintain the size the user may have changed it to by dragging the edge of the window on rerun. This is most likely due to my call to PlotInterface::SetDynamicDataTableSize(instanceName, maxRowCount, maxColCount) in DynamicDataDisplay.cpp that occurs during the Initialize() method.

            Show
            jraymond Joshua Raymond added a comment - The DynamicDataDisplay window does not maintain the size the user may have changed it to by dragging the edge of the window on rerun. This is most likely due to my call to PlotInterface::SetDynamicDataTableSize(instanceName, maxRowCount, maxColCount) in DynamicDataDisplay.cpp that occurs during the Initialize() method.
            Hide
            djcinsb Darrel Conway added a comment -

            I'm attaching the script that I used for local testing.

            Tetyana – as far as I can tell, everything is now cleaned up. Please let us know if we missed anything.

            Show
            djcinsb Darrel Conway added a comment - I'm attaching the script that I used for local testing. Tetyana – as far as I can tell, everything is now cleaned up. Please let us know if we missed anything.
            Hide
            troyzman Tetyana Royzman added a comment -

            Tested the DynamicDataDisplay window close behavior with the couple of Builds to make sure the issue resolved.
            The behavior fixed and works as expected.

            Show
            troyzman Tetyana Royzman added a comment - Tested the DynamicDataDisplay window close behavior with the couple of Builds to make sure the issue resolved. The behavior fixed and works as expected.
            Hide
            troyzman Tetyana Royzman added a comment -

            Verified successfully.

            Show
            troyzman Tetyana Royzman added a comment - Verified successfully.

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 6 hours
                  6h
                  Remaining:
                  Remaining Estimate - 6 hours
                  6h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified