SUMMARY I'm working on a python plugin (https://github.com/Larpon/krita-bulk-actions) that can trigger actions/functions on multiple nodes at once based on layer name matching. I'd like to include a way to select and deselect nodes. The reason for this is to have a way to quickly select a group of layers I want to export (currently using "Batch Exporter" from GDQuest but it's useful for all types of operations done on selected layers). Now, I can't find any calls in the API to toggle the selection state of a Node. I've found this with help from @tiar-dg on IRC: https://code.woboq.org/kde/calligra/krita/ui/kis_node_manager.h.html#_ZN14KisNodeManager16setSelectedNodesE5QListI12KisSharedPtrI7KisNodeEE My guess is that we'd also need a setDeselectedNodes or setDeselectedAll() function as well - if not already there somewhere.
The Calligra code is probably very old, the current code is here: https://invent.kde.org/kde/krita/-/blob/master/libs/ui/kis_node_manager.h
The only way I see right now to select nodes is through the document class see "setActiveNode" https://api.kde.org/appscomplete-api/krita-apidocs/libs/libkis/html/classDocument.html It doesn't look like there is a way to select multiple nodes at once. Right now you have to iterate over the nodes to do things with all of them. de-selecting might be a bit tricky since you must have at least one layer selection. For now it might be better to just set your active selection again if there are changes. We might be able to add a function like this... setActiveNodes(QList<Node *value>) where you could change the active selection to multiple nodes at one time.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I'll try and see, thanks
A function setActiveNodes would also be good
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.