Subflow without being a subflow

Core Development Feature Requests
1

I would like to be able to reduce a number of nodes to a single node.

We have subflows - however, subflows behave like a instantiation of a class and they get added as "nodes" in the palette. This is not what I am looking for, this request is more like just a visual clutter reduction of a complex flow to a single node, without it being added to the palette, nor any additional features. I can currently work around it by using a link call and have the flow living on its own tab and then hide the tab, but that's more like obfuscation and editing becomes harder.

Would it be possible to add a checkbox or option in the category pulldown to the appearance tab of a subflow, to not show it in the palette ? Not sure what the implications are when the node is removed from the flows - that may need some thought.

2

Perhaps a collapsible group would be a good fit for this?

2 Likes
3

The link call node may be for what you are searching.

You would also need the link in and link out nodes too.

But the link call allows you to make macros as you are saying.

Just a few tricks to use it.

Sorry but it is beyond my skill set.

4

As I mentioned:

5

Sorry.

I need glasses.

6

A collapsible group would actually be a great feature.
and come to think of it: group context (context that only exists within the group), could add a lot of functionality.

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.