- User Since
- Apr 22 2014, 6:04 PM (277 w, 5 d)
May 3 2019
Apr 19 2019
Apr 10 2019
Mar 26 2019
The reason that you still can register a NodeSocketColor as a type, is because it's 'internally registered' as a NodeSocket... but there are some structures/variables that are not defined in the api. The absence of those structures/values causes all sort of errors in every module that depends on them. That's why it's still an _unsupported_ feature.
Mar 18 2019
Mar 17 2019
To respond to new link events you need to use the update() and check if there's any changes in your existent sockets.
I'm still saying that there's no bug. There's no support for custom sockets, so using them is the real bug here.
If you want we can create a thread in the devtalk, for discussing this with deeper thoughts.
I'll try to take a look into this, but as far as I know, custom sockets are still incompatible with the buildin engines (unless they just have a single uniform).
My sugestion is to avoid custom sockets completly until they are supported. Try to use only _NodeSocketColor, NodeSocketFloat and NodeSocketVector_ to preserve total compatibility with Eevee, Cycles, and Compositor.
Mar 16 2019
Mar 13 2019
Fix node_clipboard_clear on exit.
Thought perhaps should be better to rewrite the clipboard functions so that we also keep a copy of the ID's. For now, python nodes that require unique nodetrees should check if the original nodetree still exists when pasting is called.
Mar 1 2019
Move freefunc_api call to nodeDeleteNode; and some minor changes
Feb 27 2019
New diff uploaded with Brecht sugestions.
Sugested Changes applied.
Feb 25 2019
Correct last revision for allowing python nodes to receive update calls
Feb 24 2019
Fixed updating (changes to the internal nodetree weren't propagating)
Add ui_hide option to nodetrees for allowing hiding them from the add menu
Feb 23 2019
Feb 19 2019
Change node->type verifications to use ELEM()
Feb 18 2019
Mar 28 2018
Nov 9 2017
Aug 13 2017
After all it was my fault.
Aug 11 2017
Changing the 2.79 folder's name, or removing it completly still produces the same error in my win10/x64 machine.
It seems a python problem. I'm using Windows10/x64 and this is the output of the error with factory settings:
Jun 1 2017
simply adding SOCK_INT to the node_exec_socket_use_stack() fixes this..
return ELEM(sock->type, SOCK_INT, SOCK_FLOAT, SOCK_VECTOR, SOCK_RGBA, SOCK_SHADER);