It looks like you use the same string for every single node. Does it really need to be stored here? I'd think you could just use the string directly in the the UI code.

The null status of one of these callbacks could check whether the GPU compositor is supported, or this could be replaced with a boolean

It looks like you use the same string for every single node. Does it really need to be stored here? I'd think you could just use the string directly in the the UI code.

The null status of one of these callbacks could check whether the GPU compositor is supported, or this could be replaced with a boolean

@Hans Goudey (HooglyBoogly) It is actually not the same for all nodes. Some nodes will have partial support, so the message will reflect that, see the Render Layers message for instance. I know having it here is not great, but it is just temporary solution until we support all nodes.

It should be noted that unspported nodes still define the callbacks, because they implement an identity version of the operation, for instance, an unsupported blur node just doesn't blur the input and pass it through.

Ah, sorry, looks like I didn't search the patch correctly. Thanks for clarifying