On Thursday, July 18, 2024 at 1:37:08 PM UTC-4 Edward K. Ream wrote:
1. There is a setting that specifies initial orientation. A plugin *could* use that setting, but a plugin could try other strategies, such as examining the widget hierarchy directly. The user might have changed the orientation so you don't want to use the initial orientation setting. IIRC, a splitter can be interrogated for its orientation. So you just get the main splitter and ask it. 2. Plugins can queue code to run after Leo's has created outline frames. [snip] We need an example plugin that shows how to do this. I suppose that it's registering for the appropriate Leo event, right? *Summary* Keep the @button prototypes dead simple. Add nifty features to the corresponding plugins if you like. @buttons are good for prototyping, all right. I even used them (in my Workbook, no less) while developing the current line highlighting code and the right margin line code. The buttons monkey-patched my prototype code into Leo's core while Leo was running. This approach let me avoid changing any Leo core code until the techniques were worked out. -- 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/f987a445-0bf6-4274-80b9-e796b2f3ce15n%40googlegroups.com.
