After a few minor changes, I have found that the problem behavior has been reduced to one circumstance that I know about. If I open VR3 as a free-floating window from the splitter, and then close it using either the close box on its title bar, or <ALT-F4> (this is on Windows, and <ALT-F4> is the standard Windows way to close a window from the keyboard), the next time I re-open VR3 using the vr3-toggle command it opens as a free-floating window with the title bar out of view at the top of the screen. If this window is moved into full view using keyboard controls, the title bar does not show the name of the associated outline. However, when I close *this* free floating window using the vr3-toggle command and then toggle it open again, it re-opens as an internal pane.
[On Windows, a window whose title bar is off-screen can be moved by pressing <ALT-Spacebar>, then <M>, then use the arrow keys to move it into full view.] It is possible that previous use of my private experimental command vr3-use-default-layout was necessary to arrive at this point, but I can't undo it to be sure. At any rate, It's clear that closing a free-floating window using other than VR3 commands causes some change in what layout is applied by Leo, or how opening the pane is called. Note that I have not tried any of this on Linux yet. Anyone have any ideas about what might be going on here? I think it is acceptable and maybe even desirable for the VR3 pane to open inside Leo's window instead of as a free floating window after it has been closed, since 1) you can always open it free floating again using the splitter bar context menu, and 2) How else could you tell Leo that you want it to stop being a free floating window? I suppose that's just where docks could have been useful, if only they could have been made to work correctly. On Wednesday, September 23, 2020 at 3:15:52 PM UTC-4 [email protected] wrote: > Some progress to report. I created a layout that puts VR3 into the > right-hand pane. This is my normal layout with the outline and log panes > at the left, body center, and VR3 at right. I wrote a command to load that > layout. No matter what has gone wrong with the layouts (like VR3 in a free > floating window with the title bar off-screen), this will open VR3 in the > right hand pane. > > Once I invoke this command, then VR3 will open, close, and re-open in the > right pane using the command vr3-show or vr3-toggle. If I open it as a > free floating window using the splitter bar context menu, VR3 will open in > its own window and its title bar will include the name of the leo outline. > > However, having done that once, when I close and reopen VR3 using the > vr3-toggle command, it will re-open as a free-floating window with the > title bar off-screen, and when moved on screen the title bar does not > contain the outline's name. In this state, the only way to get VR3 to open > in the internal pane again is to invoke the new vr3-use-default-layout > command. > > Note that this new command is not in the repo - for the time being it's > just for my own experimentation. > > On Wednesday, September 23, 2020 at 9:42:08 AM UTC-4 [email protected] > wrote: > >> Neither one returns VR3 to the internal pane. >> >> On Wednesday, September 23, 2020 at 7:27:36 AM UTC-4 Edward K. Ream wrote: >> >>> On Tue, Sep 22, 2020 at 10:01 PM [email protected] <[email protected]> >>> wrote: >>> >>>> We are not out of the woods yet. I have found that unpredictably an >>>> outline will open VR3 in a floating window, and then there doesn't seem to >>>> be a way to get it to open in the internal pane, not even closing and >>>> reopening Leo. >>>> >>> >>> Try either the "Restore initial layout" or the "Restore default layout" >>> from the splitter (Easter Egg) menu. >>> >>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/6cb13ff1-faa0-4dd1-a07b-77553e199dcan%40googlegroups.com.
