We should wait a little to see if anyone responds, shouldn't we? We know at least one person was interested enough to try using Add-Editor. Maybe there are others who haven't been updating Leo all along.
On Sunday, August 25, 2024 at 8:05:41 AM UTC-4 Edward K. Ream wrote: > On Sun, Aug 25, 2024 at 6:21 AM Thomas Passin <[email protected]> wrote: > >> It looks like the colorizer might be getting the wrong position - the >> position of the original editor rather than the newly focused position. >> Might there be a p.copy() involved here? > > > Anything is possible. > > I don't understand the code very well either, but one of the complicated >> things is that all the signaling and ivars get moved over to whichever >> editor widget gets the focus. I don't see why that was necessary since if >> the editing widget were inactivated it shouldn't receive any signals >> anyway. Maybe it would have been better to only use one editing widget and >> when the focus gets changed to the other editor panel, the first one gets >> replaced by a screen shot and the single editing widget actually gets >> inserted into the second panel. >> >> Unless there is going to be some improvement in the user interface that >> will prevent confusion about which node is being edited by which editor, I >> don't have any interest in trying to sort this thing out. >> > > Neither do I. > > PR #4047 <https://github.com/leo-editor/leo-editor/pull/4047> is ready > for review. As you can see, the PR changes little, but deletes a lot of > horrible code. > > I'll add more detail to the PR's checklist later 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/92ed7ce7-4c40-4fa4-8640-e48100c74701n%40googlegroups.com.
