On Tue, Aug 20, 2019 at 2:18 PM Matt Wilkie <[email protected]> wrote:
> I am considering switching to g.app.db for sizing Leo. That is, Leo's >> main window would open with the size it happened when it last closed, >> *regardless* of what outlines are being opened. Imo, this would be more >> intuitive for users. This would also remove some seemingly-out-of-place >> configuration code from Leo's "fast read" code. > > > I would like this to be the default. > Thanks for your vote. I do see a strong argument for being able to save and load layouts. > Activity profiles if you will. A project which is all about writing needs a > very different layout from one which is all about code which is different > from organizing a website with vr previews. > The present "sessions" machinery probably does this. Details are hard for me to remember. There are subtle interactions in various places. In some sense, Qt does almost too much automatically. Very little Leo code is involved. This is one of several considerations that will require extensive testing, on the scale of the testing required for the dock-related code in Leo 6.0. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0LMp2%3DyV%3DuzeYXWKQ9VNw4rCAjFwONSCRXoPp7BtySXA%40mail.gmail.com.
