Hi Jeremy

I’m not aware of any workaround, I think this is something that would need 
> fixing in the core. The simplest implementation would be to track the open 
> windows and then expose the details via a filter operator. We might also 
> add a message to close a specific child window. 


Oh! That'll be grand! Can that be included by the next release? I should 
probably add this to github as a feature request.

-jd
 

On Wednesday, August 12, 2020 at 3:50:08 AM UTC+9, Jeremy Ruston wrote:
>
> Hi JD 
>
> > I was wondering if the main browser window tracks its children windows? 
> I have this scenario: 
>
> No, at the moment there’s no tracking of the open child windows. 
>
> > Different drafts opened in multiple children windows through 
> tm-open-window, but are not opened in the story river of the parent browser 
> = cluttered draft tabs in the bottom of the parent browser. 
> > 
> > I experimented with populating a list tiddler (WindowList) with the 
> title of children windows as they are being called. In this way, I was able 
> to target the red draft tabs and style the specific tab so it isn't 
> displayed in the parent window. 
> > 
> > The problem now is, when I close the child window, it is still listed in 
> (WindowList) and thus its red draft tab in the parent window is still 
> hidden. 
> > 
> > 
> > Is there any workaround to this or am I missing something? 
>
> I’m not aware of any workaround, I think this is something that would need 
> fixing in the core. The simplest implementation would be to track the open 
> windows and then expose the details via a filter operator. We might also 
> add a message to close a specific child window. 
>
> Best wishes 
>
> Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev/28cc6dca-d427-41fb-8dbe-71d46c398824o%40googlegroups.com.

Reply via email to