Cannot turn on/off debug output in subflow

[Julian Knight]

There appears to be a slight issue in subflows. I've just moved a generic webpage input handler (sends all input changes back to NR over websockets) to a subflow so that I can use it in many places (adding a filter using the switch node in each case).

But I'd left a couple of debug nodes attached, one of which was turned on. I tried to turn it off but I can't, I get the message:

Warning: Node actions disabled in subflows

But that is for input triggers isn't it? Surely we should still be able to turn on/off debug output?

[Nicholas O'Leary]

Hi Julian,

Hmm, interesting point. All node actions are disabled because they only operate on deployed nodes - and a node in a subflow template isn't a concrete deployed node.

in the case of the Debug node, it also toggles a boolean flag in the node state that can be saved on deploy.... which you now cannot do as the actions are disabled.

Will have a think about how to reconcile the two. A possible fix to add a functionally equivalent option in the node's 'to' property.

Nick

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Julian Knight]

No worries nick, not a big deal but surprising.

I'm actually more pleased that I've worked out a generic method for handling ANY input changes for all forms on any page! Though I realised I haven't got buttons working yet. Getting round the problem that you cannot dynamically create websockets (e.g. 1 for each page you create).

Incidentally, I've also stumbled upon a generic way to handle client-side websocket disconnections. All thanks to the "reconnectingWebsocket" library. That has also allowed me to write a generic client-side websocket handler function that can be called multiple times on a web page if needed (to handle multiple sockets).

I'll write it all up somewhere when I get some time. Bad week at work this week so I'm going to take some downtime now.

[Kim Letkeman]

It's been 18 months since this thread was active. I am using a recent version of node-red on Windows and finding that debugging in a subflow is still not possible. I'm working on a fairly complex binary search algorithm for divergent blockchains and it would be nice to have debug functioning inside a subflow. Is there any chance that this will make it in one day?

[Tyrone Wilson]

I know it isn't ideal but I had this issue and found that it is possible to disable the node in the flow.json file. You just have to find it by name or follow the json tree to the node and set "active": false.