(I'll start this thread) :slight_smile: These are ideas/bumps (n the road) for me when I'm using the editor. //== I have LOT of tabs. I find it annoying that if I have the debug set to this flow the list is still quickly swallowed (wiped) because other flow debug nodes are included in the output queue. //== I am on a tab and editing a function node. What was that variable name I used in/on another tab? Rather than being able to go to another tab WHILE editing the node, I have to close it first. Maybe petty but it does catch me a few times and it is sometimes annoying. Particularly when it IS a function node and I am deep in the bowels of it's code. Closing it, then coming back to it is a bit distracting. (IMO) //== (This one is tricky) I have the node's documentation page open checking how to structure an inbound message. Ah! That's how I do it! and then click on the pervious node upstream from it. All that handy information is gone and my CRAFT disease sets in and I can't remember what I just saw. So I have to click back on that node try again to remember the important part then go back to the node I need to edit. Maybe it is the OCD, but with the screen change my eyes get distracted and I forget things. A way to HOLD (LOCK?) the documentation for THAT node would be nice. Then when I am making (say) a template to be sent into cron-plus I am editing the change node (example) while looking at the documentation for the cron-plus node. //== With the new Drag wire to empty space and get a requestor for next node is nice, there seems to be a positioning problem. I have a 35kb .webm clip of the example but can't upload it. Help with options. //== This is only an idea A SCRUNCH option. Let me explain, and forgive this digression. You are working on some nodes and want to make a subflow. You drag select them and select nodes to subflow. Ta-Da! They are all in a subflow. You are working on a bunch of nodes which have been giving you a headache. You have them nicely spaced as you were needing debug and inject nodes all over the place. Now, you are down to the BARE BONES of things yet the nodes populate a rather large area. The SCRUNCH would work by removing most horizontal space between nodes and most vertical space too. NO REARRANGING! Just getting rid of excess space. Maybe a pipe dream, but it may be handy for people. //== (Maybe I'm going blind, but....) :face_with_crossed_out_eyes: When I am searching for a node. It sometimes takes a lot of retries for me to actually see the node. Settings to adjust how the FOUND node is blinked.... The number of pixels wide for the orange dashed line. The colour. How long it blinks.

[image] Trying_to_learn: Yes, but the Problem there I see is that all the information is not on the one page. So people like me who can't always remember things would still have to swap pages. If you use a good browser, it should support page tiling which allows you to combine tabs in a single view. Or you can use separate browser windows and arrange them. This is why most multi-panelled tools (like code editors) end up being able to shift inner panels to external windows. Also, because so many of us have multiple active monitors. All that screen real estate and we can't use any!

[image] Trying_to_learn: I click on the node upstream to edit it and that important information is gone as I am now looking at the new node's documentation. Isn't that what the screenshot shows? The upstream node is the Inject node now being edited, the documentation pane is showing the Join node.

Ok, sorry. The meaning was lost for me when I read it. My bad.

[image] Trying_to_learn: Settings to adjust how the FOUND node is blinked.... The number of pixels wide for the orange dashed line. The colour. How long it blinks. This, i can't really see the selected/blinking node, like nr is playing games with me or something, 'please try again', freaking annoying. And it is also because the overlay is gray, that should be removed, it serves no purpose.

[image] Trying_to_learn: When I am searching for a node. It sometimes takes a lot of retries for me to actually see the node. did you see Highlight nodes in search results list which was something that kind of goes in that direction

i am heavy node-red user with 100's of automations.. few on top of my list debug node should print all properties (not just payload) by default. a central place to store the settings/credentials with user friendly UI (see this thread where I ended by creating a contrib) . Current global context requires a flow to edit/create settings and those settings are not encrypted when saved on disk. easy way to update the function import libraries('modules'? in setup tab of function nodes) to latest version

[image] hoolahoous: debug node should print all properties (not just payload) by default. Well there are alias nodes that I created. One of those is debug entire message node. This is a hack solution to do something that could be really useful for exactly that situation: different default values for existing nodes. It is a non-trivial thing to do but can be very useful.

it will be awesome to allow setting defaults for each node type so any new node dragged into console is created with the defaults.

[image] hoolahoous: it will be awesome LMFTFY :slight_smile: - ... it would be awesome...

Node-RED

Node-RED Forum

Suggestions for Node Red 5.0

Core Development Feature Requests

Trying_to_learn 4 December 2025 10:40 11

I may need to put my thinking hat on and look more into that.

Thanks.

Highlight nodes in search results list

Topic		Replies	Views
Node-RED Survey: Shaping the Future of Node-RED's User Experience News	105	3666	6 October 2025
Wish for new Nodes General function-node	24	713	20 January 2023
[Doc feature request]A more complex contrib node example Developing Nodes	24	1428	7 July 2020
:tada: Node-RED 5 now available News	86	3520	3 September 2026
A flashing node for the edit screen - requeset Feature Requests	22	680	21 March 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Suggestions for Node Red 5.0

Related topics