I didn't realize that nulling a widget's parent would make it free-floating. I suppose it makes sense. One quirk, not a fault of the script. At least with VR3 (and most likely with VR, too) if you set it free floating while it's already visible it will receive the node changed event and change its rendering as you select different nodes. If you open it and set it free-floating *before* it's been opened, it doesn't receive the node changed event and the body being rendered doesn't change. VR3 has a "Reload" menu action, and that will reload with the currently selected node.
I don't think it's worth trying to do anything about this behavior, but it's worth noting. On Monday, June 24, 2024 at 9:32:15 AM UTC-4 Edward K. Ream wrote: > On Mon, Jun 24, 2024 at 7:49 AM Thomas Passin <[email protected]> wrote: > >> Thanks for the examples. One nit: the command to detach VR uses >> c.k.simulateCommand(). Remember, we were supposed to start using the >> new c.doCommandByName(). ("Old habits die hard"). >> > > Thanks. I've updated the scripts. > > 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/beb73eb8-6d5f-4d11-8765-e110a05f016en%40googlegroups.com.
