Once a pyzo dock is closed using x or unchecking it, it is gone and cannot be reopened. The "Editors" and "Shells" docks behave correctly ie. they can be opened and closed using the right-click pop-up titlebar method. Restarting Leo restores the docks to the pop-up menu and opening them using the right-click puts them right back where they had been positioned before unchecking them. Unchecking them again causes them to vanish.
I can hardly wait to tie into theming the new objects. :-) The artifacts still persist. HTH, Chris On Wed, Aug 28, 2019 at 8:20 AM Edward K. Ream <edream...@gmail.com> wrote: > As of rev a0c34f4 in the pyzo branch... > > The pyzo_in_leo.py plugin requires --global-docks and the qt gui, which is > Leo's default. It is incompatible with --no-dock. > > Pretty much everything "just works". The plugin properly loads all pyzo > docks in *Leo's* main window only once, at "start2 time". You should see > an *Outlines dock,* containing one tab per opened .leo file. You should > also see *all* of Pyzo's docks. > > You can close any pyzo dock or relocate any pyzo dock *within the > top-level window only*. Leo will remember the configuration. The next > time you reload Leo you will see the pyzo docks as they were. > > The pyzo docks are *completely* independent of Leo. In essence, pyzo is > a guest within Leo. Pyzo itself knows nothing about Leo. Leo knows just a > bit about pyzo, and all such knowledge is confined to the pyzo_in_leo > plugin. > > *Testing* > > You will not see any of the brightly colored test docks. I am interested > in knowing whether any drawing "artifacts" appear in any dock. I don't see > any, but then I never have... > > *To do* > > The plugin doesn't remember the contents of pyzo's Files dock. More > generally, the plugins close handler should probably use *Leo's* > configuration code to save any required data. This will likely be a > "project". > > Opening a .leo file with pyzo's file browser should open the outline > within a new tab in Leo's Outlines dock. > > It remains to be seen what other changes will be desirable. > > *Summary* > > Another phase of #1093 > <https://github.com/leo-editor/leo-editor/issues/1093> is complete. Pyzo > is now an almost completely functional guest within Leo. > > The next phase will be to further integrate pyzo within the Leonine world. > > 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 leo-editor+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/a005711e-7256-4f31-ae2b-2f8c425f36da%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/a005711e-7256-4f31-ae2b-2f8c425f36da%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CADWQas0EtX7eb_9e1SoxySTkEUJzf2hArLHN9d4yT%3DnoheqcMA%40mail.gmail.com.
