Misleading save of windowLayout in GlobalAttributes section of config

[markcmiller86]

Describe the bug

This line in a .config file is totally ignored by VisIt. It should not be saved.

                <Field name="windowLayout" type="int">9</Field>

The real stuff in the .config file that drives how windows come up when VisIt is started is down near the bottom of the file where it outputs ViewerWindowManager and includes a list of windows...

            <Object name="ViewerWindowManager">
                <Object name="SelectionList">
                </Object>
                <Field name="cameraView" type="bool">false</Field>
                <Field name="viewExtentsType" type="string">AVT_ORIGINAL_EXTENTS</Field>
                <Object name="Windows">
                    <Object name="ViewerWindow">
                        <Field name="windowSize" type="intArray" length="2">1150 1147 </Field>
                        <Field name="windowImageSize" type="intArray" length="2">1150 1083 </Field>
                        <Field name="windowLocation" type="intArray" length="2">403 25 </Field>
                    </Object>
                    <Object name="ViewerWindow">
                        <Field name="windowSize" type="intArray" length="2">757 757 </Field>
                        <Field name="windowImageSize" type="intArray" length="2">757 693 </Field>
                        <Field name="windowLocation" type="intArray" length="2">1161 25 </Field>
                        <Field name="maintainView" type="bool">false</Field>
                    </Object>
                    .
                    .
                    .

That said, upon restart, VisIt will not return the windows to their original state before the settings were saved. It will create the windows but they will not fit nicely into their respective places on the screen as setting a layout would actually do.

It might be nice for ViewerWindowManager:SetFromNode to call ViewerWindowManager:SetWindowLayout upon setting up all the windows. The challenge is, it cannot really know which layout might be correct. It would have to use heuristics and guess. The user could have set a layout and then deleted a window or two or resized a window or two, etc. I suppose if after setting a layout, no windows were added or deleted and no windows were resized, then it might be ok to include information in .config what the layout id is and that it is clean and then restoring could set that layout again.