On Mon, May 20, 2024 at 10:20 AM Thomas Passin <[email protected]> wrote:
Imo, there is *no way* to have the free_layout and nested_splitter plugins > coexist with the PR. I am considering moving those two plugins to the attic. > > > I wouldn't go that far. My script tries to use the free_layout method to > find the right widget to insert VR3 into, and that raises an exception it > uses the new method instead. One could easily move the script into the > plugin itself as a command. So I think they could coexist - with some > rewriting, of course. > I'm willing to leave the two plugins where they are, untouched. However, I don't think you (or anyone else) will be able to use them reliably. In the PR, *dw.createMainLayout* creates the main and secondary splitters as QSplitters, not NestedSplitters. This change is essential. Otherwise the free_layout plugin is *privileged*, that is, baked into Leo. But the new widget hierarchy changes all of free_layout's assumptions. Imo, this will likely cause problems with the free_layout plugin. *Summary* I stand by my statement that the PR creates an environment that can not coexist with the two plugins. However, there is no harm leaving the two plugins where they are. The strategy you propose (moving scripts into the VR3 plugin) will work. I think you'll find that those scripts may as well ignore the free_layout plugin. Thomas, I'll be happy to zoom with you if you like. 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/CAMF8tS2sxBPy9kP2KPRQLgzsZGWZOhsFNcDyn3YW%3DM4R_RwSkg%40mail.gmail.com.
