I made a suggestion around that earlier today, don't know if anyone noticed?
1 Like
Yes. Just read your comment. It is the same solution.
In my opinion, fully coloring the input or output ports using a color different than the default is enough to show Users that the node is going to log messages when something passes through the node.
I liked your third suggestion. The one that you placed a green square inside the ports. But I believe it would look better if it was fully colored with green, while making the border a darker green.
Agreed. Limitations of my image editor!
The idea is if the input debug is switched on, fill the input connector.
If output, likewise.
1 Like
Doesnāt this then ācompeteā with the other request to be able to tell when wires are connected , rather than passing underneath, which is also currently being looked at by differentiating the connector pins
1 Like
Yes it does 
You are considering changing the connector fill colour when a wire is connected?
For sure there is a problem, where nodes overlay wires but are not connected, which ought to be tackled. Currently you have to move the node and watch the wires.
Changing the node fill won't help in the following situation though, you have to look at the wires.
So 95% + of connectors change colour and the issue is only resolved where zero wires are attached.
Changing the colour of a connector if no wire is connected?
Much less frequent, possibly a brighter fill (red)? in the rare occurrence.
I think this could co-exist with the "debug turned on" option, no wire connected takes precendence.
Edit - that would work for the input connector but not really for the output, where no wire connected is a viable setting.
Could one or other indication employ an outer glow, or a drop shadow effect?
Only indicate no wires on an input connector?
I bow to your knowledge and guardianship of the user interface look!
I'm just throwing up the outline of an idea to see if people like it.
1 Like
I've updated and committed an improved version. I think everything should work pretty much as the debug node does. Except that the default for status output is count rather than the same as the debug output since that's what I mostly use it for. 
Because we don't have the output button to indicate whether output is active or not, I've added a visual indicator to the label. Simply turn off all three possible outputs and the node will just pass messages straight through.
If I get 10 more subscriptions to my YouTube channel
, I'll publish this as a separate node. 
I might even do it if I get a few responses on this thread asking me to.
Otherwise, it might one day be added to UIBUILDER.
2 Likes
It installs ok now. 
-
Sometimes it doesn't work. If I untick all the outputs & deploy, then tick Debug WIndow & deploy, it does not output messages. (I have it set to complete message object)
-
Double click the node to open the config dialog. Cancel. Click somewhere else. The node label disappears. Sometimes happens when you drag the node too.
-
Although Node Status is not ticked, there is a blue dot and 0 below the node. It does not update as messages pass through.
-
I find it hard to associate the active/inactive indicator with an output. Partly because outputs are at the right and this is at the left. No doubt also because I'm used to the debug node "button" collapsing.
This is pretty good, worth adding to the palette but I don't think it will replace my use of the debug node until I can turn off it's output with a single click.
1 Like
Thanks for the unreserved praise!
Mostly it is a copy/paste from the debug node but I did spot some odd things in the code that probably need simplifying. I didn't really have much time or energy to do that I'm afraid.
If a few more people think it worth turning into a full node, I'll probably go and dig some more. Otherwise, I doubt I'll do much more on it.
1 Like
