https://bugs.kde.org/show_bug.cgi?id=480718
--- Comment #2 from Freya Lupen <penguinflyer2...@gmail.com> ---
The exact change that caused this regression seems to be this in
KisSynchronizedConnectionBase::postEvent() :
> - if (QThread::currentThread() == this->thread()) {
> + if (s_instance->enableAutoModeForUnittests && QThread::currentThread()
> == this->thread()) {
which causes the 'else' path to be taken.
In that path, the order of events when loading the document seems to change
from
> KisDummiesFacadeBase::slotNodeAdded,
> KisDummiesFacadeBase::slotContinueAddNode,
> KisDummiesFacadeBase::slotNodeAdded,
> KisDummiesFacadeBase::slotContinueAddNode,
> KisDummiesFacadeBase::slotNodeActivationRequested,
> KisView::slotLoadingFinished
to
> KisDummiesFacadeBase::slotNodeAdded, KisDummiesFacadeBase::slotNodeAdded,
> KisView::slotLoadingFinished, KisDummiesFacadeBase::slotContinueAddNode,
> KisDummiesFacadeBase::slotContinueAddNode,
> KisDummiesFacadeBase::slotNodeActivationRequested
KisView::slotLoadingFinished being where the current node is set.
I'm guessing this reordering is the cause of this bug.
--
You are receiving this mail because:
You are watching all bug changes.
