It no longer crashes for me, thanks. While it doesn't crash, it is still possible to move a node left out of a hoist and the node "disappears". If it is the last node then it disappears and the outline pane becomes empty. The existing leo doesn't behave this way. Another behavior difference. Leo doesn't allow a top-level sibling to be inserted while a node is hoisted. Instead all top-level insert operations are forced to be child insertions.
Maybe the behavior you have is reasonable, but it doesn't match the way leo operates. I'm just pointing these out to let you know. Probably polishing the prototype is not as important as figuring out how to proceed to see how/whether it can replace the existing qt gui. On Sat, May 9, 2020 at 4:48 PM vitalije <[email protected]> wrote: > Good catch Brian. Revision 8184a2023e5f9 contains the fix for this issue. > Now hoist/dehoist commands are also tested using hypothesis. > > Vitalije > > -- > 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/ede74c56-e1b8-44e7-adb5-85a07b9355e8%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/ede74c56-e1b8-44e7-adb5-85a07b9355e8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAO5X8Czv%3DZaFYmV5Y7s3vERTMaD_v98c%2BcHf15phk%3DVXX%2B%2Bt1g%40mail.gmail.com.
