Re: ENB: Saving restoring layouts

On Monday, October 5, 2020 at 3:30:12 PM UTC-4, Edward K. Ream wrote: > > ... > >> >> I had slightly modified this code. But when I restored it to your >> version, I still found that a new ViewRenderedController3 object gets >> instantiated each time the rendering panel gets hidden and then

Re: ENB: Saving restoring layouts

On Mon, Oct 5, 2020 at 1:12 PM Thomas Passin wrote: > I presume you are referring to the code in the command "vr": > > @g.command('vr') > def viewrendered(event): > """Open render view for commander""" > global controllers, layouts > if g.app.gui.guiName() != 'qt': > return

Re: ENB: Saving restoring layouts

I presume you are referring to the code in the command "vr": @g.command('vr') def viewrendered(event): """Open render view for commander""" global controllers, layouts if g.app.gui.guiName() != 'qt': return None c = event.get('c') if not c: return None h =

Re: ENB: Saving restoring layouts

OK, I'll take a look at that. On Monday, October 5, 2020 at 11:45:31 AM UTC-4, Edward K. Ream wrote: > > > > On Sat, Oct 3, 2020 at 7:41 AM tbp1...@gmail.com > wrote: > >> There are two widgets involved here. One is the actual displayed widget, >> such as a QWebView. That's the one checked by

Re: ENB: Saving restoring layouts

On Sat, Oct 3, 2020 at 7:41 AM tbp1...@gmail.com wrote: > There are two widgets involved here. One is the actual displayed widget, > such as a QWebView. That's the one checked by vr3.ensure_text_widget(). > The other one is the ViewRenderedController3 itself, which is not a > display widget in

Re: undoing unmarks nodes

On Mon, Oct 5, 2020 at 3:40 AM gar wrote: > I reported that long time ago. Actually I do observe that marks > disappear even w/o undo, sort of suddenly. The new #1694 suggests a thorough review of the marked bits logic. Edward -- You

Re: undoing unmarks nodes

I reported that long time ago. Actually I do observe that marks disappear even w/o undo, sort of suddenly. Since I didnt use clones for my @auto code files - I used marks intensively to quickly switch btw various code-in-work nodes and was totally upset with how they do behave. Again, just