On Sat, Jul 20, 2024 at 1:53 PM Jacob Peck wrote: The vr-related crashes are already happening in Leo, I reported a bug on it > earlier this week: https://github.com/leo-editor/leo-editor/issues/4009 >
Thanks for the link. I was not aware of the issue. I suspect it's the same bug, and nothing new your scripting and tests are > causing :) > I wouldn't put it that way. #4009 presumably happens because the VR/VR3 controller isn't properly destroyed. That bug should be relatively straightforward to fix. But ideally, a layout undoer should preserve the *existing *VR/VR3 controller and its gui. You would think it would be straightforward to "relocate" the VR/VR3 pane, but I haven't discovered how to do that yet. There seems to be a hole in the QSplitter API. As if that weren't enough, both the VR and VR3 startup logic can create different widgets (in different places) depending on user settings! It's a puzzle. Edward P.S. The free_layout controller sidestepped these issues by creating the VR/VR3 controllers (and widgets) *after* changing the splitter arrangements. That strategy is not available to us in this project. That does *not* mean we would be better off using the free_layout plugin! EKR -- 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/CAMF8tS2BRRyrhAyF%3DE2YywpEq%2Bip95um-L34va2LNQXL8C%3DH7g%40mail.gmail.com.
