On Wed, Aug 28, 2019 at 10:58 AM Chris George <[email protected]> wrote:
Once a pyzo dock is closed using x or unchecking it, it is gone and cannot > be reopened. The "Editors" and "Shells" docks behave correctly ie. they can > be opened and closed using the right-click pop-up titlebar method. > Restarting Leo restores the docks to the pop-up menu and opening them using > the right-click puts them right back where they had been positioned before > unchecking them. Unchecking them again causes them to vanish. > Yes, I see this. Some/all of this may be the result of the most recent work. Hehe, I saw all this, and more, when showing off my work to Rebecca. Sure enough, demos always fail. If you revert to rev 2364cd0d you will see different behavior. It doesn't suffer the bugs you have reported, but alas, it can't be the basis for future work. I'll get to the bottom of this next. I can hardly wait to tie into theming the new objects. :-) > Glad you mentioned this. The latest work attempted to get rid of c everywhere. That won't work, because we need a commander to get theme settings. The new code will use g.app.commanders()[0]. It is the commander of the first loaded .leo file The artifacts still persist. > Please send a screenshot. This might be a gotcha. Nesting QMainWindows inside other QMainWindows might stress Qt beyond the breaking point on some platforms. HTH, > It helps a lot. Please remind me what platform you are using. *Summary* I'm a bit surprised by these newly-reported bugs. Fixing them should be possible, but I'm not sure how long it will take. Chris, please send a screen shot showing the "artifact", and remind me what platform you are on. It's time for me to test on Linux. 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/CAMF8tS12dgzAwj6wV-B_Q-x0qvUPcW1zLY4bJOhrsnekRe3YKQ%40mail.gmail.com.
