Open sdugloudYBG opened 1 year ago
Hi @sdugloudYBG, you can disable this behaviour by searching for the setting Better Wiring For New Nodes
. This is a good point, in this case it makes sense to insert the node after the last usage. But I'm not sure if the user would always want this to occur, although I think in the majority of cases this would be the preferred behaviour. I'll try to have a look at this in the future.
Update about this in the latest version: 4.2.0. I have not changed the behaviour of this setting. However I have removed the Better Wiring For New Nodes
setting and split it into 3 seperate settings. From the changelog:
Better wiring for new nodes
and add 3 new settings in Blueprint Assist Editor Features
Connect Execution When Dragging Off Parameter
When creating a new node from a parameter pin, try to connect the executionInsert New Execution Nodes
When creating an executable (impure) node from a pin, try to insert the node between existing wiresInsert New Pure Nodes
When creating a pure (parameter) node from a pin, try to insert the node between existing wiresThese are all true by default, so you will likely want to disable the Insert settings.
Hello!
When I create a function call node from an output object, it inserts the new node in between the selected node and the next one (I wasn't able to find what's the official name of that feature :P).
While I see the usage of this in certain case, more often I'd like the new node to be linked at the end of the execution flow and not be inserted in between. This is especially true when I have a IsValid node after a Getter impure node. It can get annoying to do sequence stuff on an object after a IsValid node due to that feature.
Would it be possible for the feature to insert the new node after the last node that uses the output ? (In my case, after the IsValid). Or, can I locally disable it if there is no good solution for that ? (As I don't know the name if it, I don't know what to disable ^^).
Thanks in advance for your help :) .