It's somewhat akin to undo/redo. I would say. No matter what the details, the undo or restore code still needs to know how to delete added GUI widgets. That's where a teardown() API method comes in. On Sunday, July 28, 2024 at 10:11:19 AM UTC-4 Edward K. Ream wrote:
> On Sun, Jul 28, 2024 at 3:04 AM Edward K. Ream <[email protected]> wrote: > > The PR will soon contain hard-coded methods that define all Jake's >> suggested layouts. >> >> When that work is complete, I'll start work on *@data qt-layouts*. >> > > @data qt-layouts is a wretched idea. The advantage of writing up bad > ideas is that they can be killed before doing any work on them ;-) > > Why create a half-baked description language when plugins can execute Qt > code safely? A new Leo event, > > * g.doHook("after-create-layout-dict", c=c, layout_dict=layout_dict)* > > should allow plugins to define one or more bespoke layouts. I'll test this > theory today. > > 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/b83f7093-6e82-4a7b-8585-e67b69abed2cn%40googlegroups.com.
