Reply To: Feature: Flowanvas Macros for usage in Nodecanvas Action-&ConditionTasks

[dave]

1) Nice to hear that I am not the only one who thought about this

2) AH, I see , the fruits are not as low hanging as they seemed :). Maybe if there was an option to explicitly tick/mark a nested FC-Node( or even multiple ones ) as jump-into-node as soon as it gets instantiated/ activated, that would be totally sufficient. Until instantiation , nothing to watch there anyways.. even better & more interesting to watch what happens on the above layers. The feature would be as simmple in usage as setting breakpoints is . ( Probably would have to prioritize when running nodes concurrently, but other than that…). The exhausting part of the process is the exiting of the player window, fiddling into canvas ,clicking into node,…..,….. Its not a problem to not being able to see the node immediately,there’s no need to see the node’s content immediately after entering playmode. I know, coming up with feature suggestions is so easy 🙂 But as long as you invest in support for your product, I will support you with providing suggestions maximize usability of the framework 😀 Thank you, and have all a nice weekend