The docks2 branch is ready for testing

[Edward K. Ream]

Rev bf16967 in the docks2 branch implements #1268, persistent body editors.

This is a major piece of work. I would be shocked bugs were not found. Please test the code and report any problems.

The new code writes more entries to c.db. It probably won't cause any cache problems, but we shall see.

Writing to c.db means that editor docks in all open .leo files should be saved, but I haven't tested this.

Edward

[Thomas Passin]

Leo 6.2-b1-devel, docks2 branch, build bf16967989
2020-03-05 11:33:41 -0600
Python 3.8.0, PyQt version 5.14.0

Windows 10 AMD64 (build 10.0.18362) SP0

A 2nd editor window was persisted.  But for the first restart, the 2nd editor pane was docked in the upper left corner and was very small, just the way it was when I first created it.  I did a CTRL-S save, restarted Leo, and after that the 2nd editor was where I had placed it (in the right-most docking area).

I have noticed this kind of thing before.  Either Leo has to be restarted several times before a changed pane arrangement sticks, or possibly after a CTRL-S then restart it will arrange as expected.  It's hard to be definite because the behavior is erratic.

[Edward K. Ream]

On Thu, Mar 5, 2020 at 2:09 PM Thomas Passin <tbp1...@gmail.com> wrote:

Leo 6.2-b1-devel, docks2 branch, build bf16967989
2020-03-05 11:33:41 -0600
Python 3.8.0, PyQt version 5.14.0

Windows 10 AMD64 (build 10.0.18362) SP0

A 2nd editor window was persisted.  But for the first restart, the 2nd editor pane was docked in the upper left corner and was very small, just the way it was when I first created it.  I did a CTRL-S save, restarted Leo, and after that the 2nd editor was where I had placed it (in the right-most docking area).

Saving should not affect caching, which happens whenever Leo closes.

There may be a few glitches initially, depending on the state of your caches, which of course is opaque even for you.

Let me know if problems persist.

Edward