https://bugs.kde.org/show_bug.cgi?id=520729
Bug ID: 520729
Summary: setActiveNode activates WRONG node sometimes
Classification: Applications
Product: krita
Version First 5.3.2
Reported In:
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
I have addon that selects layer with python API
```
doc.setActiveNode(layerNode)
doc.waitForDone()
```
With Recent 5.3.2 activating layer via API activates wrong Node sometimes, not
the one in layerNode.
It happens sporadically, the console prints a warning: "WARNING:
TimelineFramesModel::slotCurrentNodeChanged: node not found!"
When this warning happens - wrong node is selected. Node is perfectly valid,
not a None, it is found by doc.nodeByUniqueID before call with some extra
logic.
I failed to create reproducible KRA file. Probably the reason my KRA is really
heavy on hierarchy (many different layers with clones, filters, groups, some
groups closed etc)
It worked flawlessly in 5.3.1
SOFTWARE/OS VERSIONS
OS: macOS 26.5
Krita Version: 5.3.2 (git 7d1ae74)
Qt Version (loaded): 5.15.7
--
You are receiving this mail because:
You are watching all bug changes.
