Persistent Node Browser option

This was brought up several times already over the years (tired emoji here).
Please make an option/button/node/whatever to keep the node browser open, please.
I am not going to repeat all the arguments why it would be a huge ux improvement (especially for new users) and why the current (only) behaviour is so annoying. I am just deeply disappointed that this feature request seems to have such low priority in development. Remember the NodeBrowser node from beta? Good old times (nostalgic, sad emoji here).

11 Likes

Adding another coin to this one!

This would be super useful for exploring libraries: sometimes you want to show a category and add a bunch of nodes from it in a row, and only then play with them (or throw a bunch of node in your patch and only then decide which one you’ll use).

Since the node is created at the cursor position, I guess that would require being able to drag the node to the patch?

Thanks!

7 Likes

this is such a no brainer essential feature to have in a node based programming environment with a super heavy node set. yet again an other year passed with hours wasted on annoying, repetitive clicking and typing through categories over and over again…

3 Likes

And please bring back the node search feature from the Beta: two or more character sets separated by a space allow you to find a node that includes all the described parts of the node in any order.

1 Like

CTRL+click to open the node and keep the browser open in the current category, SHIFT+click to keep open and go back to default/main category