Recent changes to devel

[Edward K. Ream]

Today I merged four PRs into devel and made some other changes:

PR #2876: Add annotations to freewin.py.  Oops! Another commit was necessary to correct the `@file node`.

PR #2877: Problems with todo.py. This PR simplified the code, but did not reveal glaring performance problems. Imo, no further work is needed now.

PR #2879: A version-related tweak to leoBridge.py. Félix, please take note.

PR #2880: Remove c.redraw_after_icons_changed. Non-trivial, as several methods defined this method. However --gui=console and --gui=browser both work.

As noted in the previous post, updating LeoPyRef.leo is can lead to huge diffs. Afaik, the version of LeoPyRef.leo in devel is correct.

Summary

Leo 6.7.0 should be code complete, but all these changes deserve further testing. Happily, more than a week remains before Leo 6.7.0 goes out the door.  Please report any problems immediately.

Edward

[Thomas Passin]

I see an improvement in that on my Windows system, the freeze time when saving LeoPyRef is now only a few seconds instead of the previous 20 - 30 seconds.  That's a worthwhile improvment!

[Edward K. Ream]

On Tuesday, September 20, 2022 at 11:32:49 AM UTC-5 tbp1...@gmail.com wrote:

I see an improvement in that on my Windows system, the freeze time when saving LeoPyRef is now only a few seconds instead of the previous 20 - 30 seconds.  That's a worthwhile improvement!

Glad to hear it! It's possible that the simplifications had greater effect than I thought.

And thanks for your testing.  Feel free to disable todo.py now, hehe.

Btw, the todo PR fixed several Qt crashers, which never would have happened if I had not had to study the code closely and test it more thoroughly.

Edward

[Edward K. Ream]

On Tuesday, September 20, 2022 at 11:14:39 AM UTC-5 Edward K. Ream wrote:

> Leo 6.7.0 should be code complete.

Now devel is more complete :-) I have just merged PR #2881 into devel.

Absent new bug reports, I plan no further changes for Leo 6.7.0. Let the testing continue!

Edward

[Thomas Passin]

Great!  Can we set up a new milestone, say 6.7.1, so that we can set a target for new issues?

[Edward K. Ream]

On Tue, Sep 20, 2022 at 11:55 AM Thomas Passin <tbp1...@gmail.com> wrote:

Great!  Can we set up a new milestone, say 6.7.1, so that we can set a target for new issues?

Done: 6.7.1 issues.

Edward