Leo's code is a behemoth. Nothing we can do is going to drastically shrink it, or make it a snap to understand or change.
Imo, using Qt's signals more effectively is likely to be the best way to simplify Leo's code *just a little bit.* This page <https://www.riverbankcomputing.com/static/Docs/PyQt5/signals_slots.html> explains the benefits. Signals aren't a panacea. Understanding signals and their interactions isn't trivial. However, cff <signal name> gives an excellent overview. I don't have any immediate plans to use more signals in Leo. However, I would welcome any experiments in this direction. 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/c744c586-929e-4229-b2b0-9c4166d40eb1%40googlegroups.com.
