You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
Now that window configurations are no longer bound to frames, a new set of possibilities opens up. There is no more need for storing them in frame-local variables. Asides from that, the behaviour per frame could be tuned on a fine basis. For example, the list of window configurations could be global and the currently selected one frame-local. Other things to think of would be commands taking frames into account, such as throwing a window configuration from one frame to another one.
The text was updated successfully, but these errors were encountered:
Does this mean I can have one global set of window configurations and share those between all the frames? Create a view on frame1 and then apply it on frame2?
Yes. Previously applying a window configuration to a different frame than it was created from did fail, now this is possible to do, as long as both frames are of the textual or graphical type.
Now that window configurations are no longer bound to frames, a new set of possibilities opens up. There is no more need for storing them in frame-local variables. Asides from that, the behaviour per frame could be tuned on a fine basis. For example, the list of window configurations could be global and the currently selected one frame-local. Other things to think of would be commands taking frames into account, such as throwing a window configuration from one frame to another one.
The text was updated successfully, but these errors were encountered: