On Wednesday, October 9, 2024 at 9:42:49 AM UTC-4 Edward K. Ream wrote: On Wed, Oct 9, 2024 at 8:11 AM Thomas Passin
>> EKR: I haven't been able to have both VR and VR3 panes open simultaneously. This looks like a bug, but imo the "devel" branch is good enough to release as it is. I have them both enabled and visible right now. It's never been a problem. When an outline opens, it doesn't have a VR3 instance, whereas it does get a VR instance. With the current code, the "vr3" command creates an instance but doesn't show it. "vr3-show" or "vr3-toggle" are needed to actually see the instance. Each of them will create an instance of VR3, even if it's not been enabled in myLeoSettings.leo. Currently, "vr3-toggle" looks to see if it already has a slot in the layout and it will become visible there if so. Otherwise, it will get added to the main splitter. I bind "vr3-toggle" to Alt-0 and "vr-toggle" to Alt-F10. I find this to be easy and convenient. The reason I don't automatically create a VR3 instance when an outline opens is that instantiating a VR3 object seriously messes up the display. You've probably noticed a big flash and the Leo window may even distort or move for a second. These effects are even worse on Linux. It seems to be something to do with Qt creating a Chrome instance and then packaging it into a Qt widget. Chrome is so big and complicated that it takes some little while. None of the usual Qt tricks for suppressing redraws have helped - I suppose it's outside Qt's control. I think these effects could be unnerving for a user, so I don't like to force them to occur when any outline gets opened, even if the user will never use VR3 with that outline. -- 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/6da53b21-45b8-490b-aada-cb73c0d418bdn%40googlegroups.com.
