PythonApi - Select nodes from script

Thank you for the detailed feedback. These are fair points we have discussed in the past.

While powerful tools can definitely be achieved with our API, I agree there are structural problems and some tasks are convoluted for no obvious reason.

I have shared your feedback internally for discussion.

Have a pleasant rest of the week!

Thanks @Luca Giarrizzo , Having used the designer api off and on for a few years I always feel like it really needs some love overall...It feels very unpythonic and more like a brute force wrapper around C++ or something. 

From a tools perspective it does feel like a chore to look through the docs to try to figure out how to interact with nodes rather than get on with building things with it.

E.g. Getting the outputsize of an output node - I can see in the graph when it says 2048 under it, but it feels like it could be a lot easier to get this information in the api 

In this example, it feels like I should just be able to do:

import sd
ctx = sd.getContext()
app = ctx.getSDApplication()
graph = app.getUIMgr().getCurrentGraph()
output_nodes = graph.getOutputNodes()
print("\n".join([x.getOutputSize() for x in output_nodes]))

Instead of this - having to get properties, transform it into another class to then get the size of it...

import sd
from sd.api.sdproperty import SDPropertyCategory
from sd.api.sdvaluetexture import SDValueTexture

ctx = sd.getContext()
app = ctx.getSDApplication()
uiMgr = app.getQtForPythonUIMgr()

def get_output_size(node):
    prop = node.getProperties(SDPropertyCategory.Output)
    value = node.getPropertyValue(prop[0])
    sd_texture = SDValueTexture.get(value)
    size = sd_texture.getSize()
    return size

graph = app.getUIMgr().getCurrentGraph()
graph.compute()
for node in graph.getOutputNodes():
    size = get_output_size(node)
    print(f"{node.getDefinition().getLabel()} size is {size}")

 I assume part of it is there's probably output nodes that "don't have a size" or something but surely there must be a more userfriendly/dev friendly wrapper that could be made - especially since it doesn't feel like we have full access to the capabilities of designer from this api as it is currently..