# Easy node access. Is this another option?
**URL:** https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084
**Category:** Core Development
**Created:** [9 June 2020 22:02 UTC](https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084 "2020-06-09T22:02:55Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2020 22:02 UTC](https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084/1 "2020-06-09T22:02:55Z")
I was just corrected about the way to access nodes in the edit screen with `Control` Left Mouse Button. (^LMB)
Though I don't use that option - yet - The entire layout of the left panel where the nodes are shown is _problematic_ in some cases. And yes, I get it: You can't please all the people all the time.
But my _twists_ on it are these:
1:
It is nice to have `subflows` at the top; until you get a few of them. Then it is annoying.
Shrinking/collapsing them is ok, until you search for the next node and close the search. The collapsed `subflow` list is again expanded.
2:
_Favourite nodes_. (Or: Often used nodes)
Which may be along the lines of the `^LMB` option.
I've found that I seem to use a small sub-set of nodes a lot for most of my stuff.
But they are from a few different sections/_branches_ of the node list (tree).
Now and then I need to get an _exotic_ one, which is access either by scrolling or searching.
That then introduces the _collapsed group_ problem when I exit the search.
With a manually set collapsed state: what about a user defined _list of often used nodes_?
This would be a **copy** of the nodes in the list. That way so as to not confuse (or trap) the user if the go off searching for the node when it is in their _favourite_ list (and collapsed)
( 😉 )
Just a thought.
Thanks for looking/reading.
---
### Author:  [@ristomatti](https://discourse.nodered.org/u/ristomatti)
#### Post date: [9 June 2020 22:44 UTC](https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084/2 "2020-06-09T22:44:54Z")
You can reorder the palette categories in `settings.js`: [https://nodered.org/docs/user-guide/runtime/configuration#editor-configuration](https://nodered.org/docs/user-guide/runtime/configuration#editor-configuration)
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [9 June 2020 22:46 UTC](https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084/3 "2020-06-09T22:46:47Z")
Thanks.
Hadn't though of that.
But the main idea of this is that you have a new category with mixed nodes from mixed parts of the list.
---
### Author:  [@ristomatti](https://discourse.nodered.org/u/ristomatti)
#### Post date: [9 June 2020 22:47 UTC](https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084/4 "2020-06-09T22:47:15Z")
Also you can assign a category for your subflows from their configuration if I remember correctly.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [8 August 2020 22:47 UTC](https://discourse.nodered.org/t/easy-node-access-is-this-another-option/28084/5 "2020-08-08T22:47:18Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.