View Single Post
Old 12-22-2019, 05:54 PM   #64
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 22,273
Karma: 124547460
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Does it happen with Sigil 0.9.18 at all?
No. It doesn't seem to with similar steps anyway. Tested 0.9.18 on Windows with Qt5.12.3 and Linux with Qt5.13.2.

The bug hitting Sigil 1.0.0 on Linux with Qt5.13.2, but not with Sigil 0.9.18 on Linux with Qt5.13.2 would seem to clear Qt of any fault, I think.

EDIT: Debug output shows that FlowTab::SplitSection() is definitely being called multiple times. As is MainWIndow::CreateSectionBreakOldTab()

TabManager's OldTabRequest signal is hardwired to FlowTab's OldTabRequest signal. FlowTab emits its own OldTabRequest signal in SplitSection(), and MainWindow connects TabManager's OldTabRequest signal to it's own CreateSectionBreakOldTab method.

Not sure if that helps, but it made my head hurt to follow that all around!
.
It's almost like closed tabs aren't getting properly disconnected from signals or something (that's a WAG on my part, though).

Last edited by DiapDealer; 12-22-2019 at 06:38 PM.
DiapDealer is offline   Reply With Quote