# Editor Feature Request - Flow List Quick Navigation

**URL:** <https://discourse.nodered.org/t/editor-feature-request-flow-list-quick-navigation/3634>\
**Category:** Feature Requests\
**Created:** [2 October 2018 19:33 UTC](https://discourse.nodered.org/t/editor-feature-request-flow-list-quick-navigation/3634 "2018-10-02T19:33:05Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 October 2018 21:01 UTC](https://discourse.nodered.org/t/editor-feature-request-flow-list-quick-navigation/3634/9 "2018-10-03T21:01:12Z")

</div>

@redDawn - yes I think there is _something_ to be done here. Although it does need some more thought.

We know that having a large number of tabs makes the horizontal scrolling of the tab bar impractical. A drop-down is an attractive choice - but it can't just substitute an unwieldy horizontal list for an unwieldy vertical one. So maybe that dropdown should have a filter at the top to make it easy to search the list - but that's much the same as using the existing Ctrl-F search box.

As is often the case, writing that down has made me stumble over another option I prefer. Rather than a dropdown, it's a button that opens the existing search dialog with the search-term pre-filled to `tab` (a capability Dave recently added in the `dev` branch... good one Dave). That saves a lot of time and effort in creating new UI.

What do you think?

> [@tilleul](#):
>
> I have created a config node called "Tab manager"

@tilleul - that looks interesting. I have had in the back of my mind to create a sidebar tab that gives a tree hierarchy view of your complete configuration - similar to the Dashboard sidebar tree. There are a number of actions that would benefit from having that sort of view.

There's a separate [thread on locking nodes/flows](https://discourse.nodered.org/t/the-option-to-lock-node-positions-in-the-designer/3092/10) (but as I go to find the link to that topic, I see you've already comments on it...)

Hiding a flow... not sure. There's enough going on in this topic, so going to politely ignore that part.

> [@hotNipi](#):
>
> ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/6/69e5630bf7c8515521f175e6b86f593e19a4d8ec.png)

Interesting idea. We've long discussed the Link node's appearance. I can see the appeal of having an option to hide the label, but I'm not a fan of it being a special behaviour if the name property is `" "`. I'd see this as being an explicit toggle option on the `appearance` tab of the edit dialog (along side the node icon/port labels etc).

The editor already shows a tooltip if you hover on a port with a label. I have pushed to the `dev` branch the ability to have a tooltip on the node body, which displays its label.

![](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/0/080c7c97b95776e3e54a1173710ec4c6e11379b2.gif)

Despite what you see in that image (which was taken whilst I was playing...) the `dev` code only uses this tooltip on the Link node (as it already hides its label). But it lays some ground work for if/when we enable hiding the label on any node.

---

_[View the full topic](https://discourse.nodered.org/t/editor-feature-request-flow-list-quick-navigation/3634)._