I don't think it's the new code, as I said on the other thread. I think there are some Qt problems in general, but I don't think they are from this. I've submitted a new PR that has a setting that needs to be set to True to enable the new behavior.
The code did require something new, and I suppose it's possible that it matters. To get the ItemEntered event to be emitted, "mouse tracking" has to be turned on for the tree. By default Qt has this disabled. I don't know why it would matter, but presumably there would be more mouse events generated than there used to be. On Sunday, March 26, 2023 at 8:29:44 AM UTC-4 Edward K. Ream wrote: > Rev 74bf72e > <https://github.com/leo-editor/leo-editor/pull/3217/commits/74bf72eee1fde545aad1a4d87b033563d2904bf5> > > (PR #3217 <https://github.com/leo-editor/leo-editor/pull/3217>) in devel > reverts PR #3214 <https://github.com/leo-editor/leo-editor/pull/3214>. > > I don't know for sure what caused a recent hard crash, but PR #3214 is a > likely culprit. Leo's tree code is notoriously fragile. > > Imo, I have no choice but to revert the recent code. > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c6739dea-1469-48bc-ac87-69efddb0d9b8n%40googlegroups.com.
