# Link-call nodes: visually showing the connections to link-in node

**URL:** <https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396>\
**Category:** General\
**Created:** [17 September 2023 11:08 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396 "2023-09-17T11:08:25Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [17 September 2023 11:08 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/1 "2023-09-17T11:08:25Z")

</div>

Hi There!

I have come to use link-call nodes extensively and one thing I find difficult is seeing the connection to the link-in node. I can open the side-panel with all link-in nodes and the node that the link-call is connected to but I _don't see_ this on the workspace, a-la link-in and link-out nodes that are connected by dashed lines.

I was wondering whether there are plans to change that? Find the connection to the corresponding link-in node is also harder since the name (shown on the link-call node) is only visible (in the workspace) when the mouse goes over the link-in node.

I have no idea how to improve this especially since link-calls have connections in and out and adding separate dashed lines would be difficult and confusing ...

Cheers!

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [17 September 2023 12:11 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/2 "2023-09-17T12:11:43Z")

</div>

During development of the link call node there were various tryouts for visually indicating linkage but in the end, visually, there was no good fit. At least not in the current standard. It is pretty easy for me to sit here and propose various solutions or ideas (like many of us did during the live stream development of the link call) but nothing really made good or practical sense (note time scale was also a constraint - an async solution or idea of the forum doesn't have that rigid constraint).

Note: I was gonna see if I could find the live stream but I am now doubting my sanity (did that really happen?)

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [17 September 2023 14:18 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/3 "2023-09-17T14:18:57Z")

</div>

One suggestion I would make is to have a "jump to" button in the listing:

![Screen Shot 2023-09-17 at 16.12.28](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/e/ce516c06c5d32fbf75ac105d0fa695f3e1b9127f.png)

I did something similar with mouse-over (i.e. a list of nodes and when I'd go over with my mouse, it would highlight that node) and found that I soon lost the plot and needed the "Back Home" button to bring me back to the original node (in this case the link-call node). In my use case, the side bar was always open because I wanted to spring to various nodes.

That's not really a visual thing but it does help in navigating the link and makes the listing more useful.

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [17 September 2023 18:32 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/4 "2023-09-17T18:32:46Z")

</div>

There is probably a good reason why this would not work - but why not the link dashes as per standard link nodes?

Also, is it possible to have a way of sorting the link end points in a link node (by flow)?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [17 September 2023 19:27 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/5 "2023-09-17T19:27:26Z")

</div>

> [@Buckskin](#):
>
> but why not the link dashes as per standard link nodes?

The link call node would need dashed lines from the inside of the calling node to the called flow and then another back to the inside of it before continuing out the exit pin on the calling node.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [17 September 2023 20:33 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/6 "2023-09-17T20:33:28Z")

</div>

> [@Buckskin](#):
>
> There is probably a good reason why this would not work - but why not the link dashes as per standard link nodes?

Because link calls can have connections at both ends (unlike link-in and link-out that have one side free), hence a dashed line along with a normal wire would be confusing.

> [@Buckskin](#):
>
> Also, is it possible to have a way of sorting the link end points in a link node (by flow)?

Aren't they grouped by flows in the side panel? Do you mean that they should be sorted within the group?

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [17 September 2023 21:37 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/7 "2023-09-17T21:37:54Z")

</div>

> [@Buckskin](#):
>
> but why not the link dashes as per standard link nodes?

And link-call nodes can be dynamic, linking to msg.target.

It is potentially misleading to bave some virtual wires as dashes on the editor and some not.  
Is there another way of clarifying these links?

---

<div class="post-metadata">

**Author:** ![Buckskin](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@Buckskin](https://discourse.nodered.org/u/Buckskin)\
**Post date:** [18 September 2023 20:15 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/8 "2023-09-18T20:15:58Z")

</div>

> [@gregorius](#):
>
> Aren't they grouped by flows in the side panel? Do you mean that they should be sorted within the group?

Yes, with a lot of links it becomes a bit of a chore to find the one you are looking for. (as far as I can tell they are in the order added)

PS I am aware that there is a search function

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [19 September 2023 07:52 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/9 "2023-09-19T07:52:16Z")

</div>

> [@Buckskin](#):
>
> Yes, with a lot of links it becomes a bit of a chore to find the one you are looking for. (as far as I can tell they are in the order added)

Perhaps something like "sort by" dropdown in the side panel would be an idea. But then there would be a need to be a setting of default sort by criteria.

Would it might be cool to have be something similar to the new 3.1.x wire-connect-dropdown:

![Screen Shot 2023-09-19 at 09.49.51](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/2/f2090ec379ab97e2b6641254a5521e406c281e24.png)

Perhaps doing the same on a link-call node would give a tree structure of all flows and then all link-in nodes in a flow. #justanidea

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [19 September 2023 08:17 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/10 "2023-09-19T08:17:20Z")

</div>

> [@gregorius](#):
>
> Would it might be cool to have be something similar to the new 3.1.x wire-connect-dropdown

FWIW, that was always present (if you held CTRL when you start wiring).

`<off-topic>`  
PS, if you hold CTRL while wiring between nodes, it go's into a quick connect mode.  
 ![chrome_iJJ2gwwNrj](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/c/cc72a3e2a15e4cc63c684558787250691793b6dd.gif)  
`</off-topic>`

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [19 September 2023 08:40 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/11 "2023-09-19T08:40:03Z")

</div>

> [@Steve-Mcl](#):
>
> FWIW, that was always present (if you held CTRL when you start wiring).

Not in my firefox with NR 3.0.2 on macOS - neither ctrl nor cmd bring up the same menu ☹

But Shift+cmd does activate the quick connect mode but I can't get the menu...

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [19 September 2023 09:12 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/12 "2023-09-19T09:12:22Z")

</div>

> [@gregorius](#):
>
> > [@Steve-Mcl](#):
> >
> > FWIW, that was always present (if you held CTRL when you start wiring).
> 
> Not in my firefox with NR 3.0.2 on macOS

FF on Mac - asking for trouble! 😉

Joking aside, I should have been clearer. If you hold CTRL or CMD (I forget which) before (and during) starting a wire from an input or output, then you click in whitespace, you _should_ get the quick-add dropdown.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [19 September 2023 09:26 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/13 "2023-09-19T09:26:07Z")

</div>

> [@Steve-Mcl](#):
>
> then you click in whitespace, you _should_ get the quick-add

should, would, could, didn't!

I only got it going via the context menu:

 ![Screen Shot 2023-09-19 at 11.18.57](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/3/d330c23ba2cb83b79af4555c6e2e0d2fa0d8aa75.png)

Some combination of ctrl, cmd, shift and mouse button down (same as using emacs) brought it up _while_ I still had a wire at the end of the mouse cursor! 🙂

> [@Steve-Mcl](#):
>
> FF on Mac - asking for trouble! 😉

Life is hard being green ... as Kermit said.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [19 September 2023 09:33 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/14 "2023-09-19T09:33:43Z")

</div>

ok, so maybe that part is broken (due to FF/Mac/combo) but I would have thought the simple `CTRL` + click (in whitespace) would work (or have been reported as not working by now)

[https://nodered.org/docs/user-guide/editor/workspace/nodes#quick-add-dialog](https://nodered.org/docs/user-guide/editor/workspace/nodes#quick-add-dialog)

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [19 September 2023 09:41 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/15 "2023-09-19T09:41:24Z")

</div>

@gregorius

On the Mac it works fine but you need to use the `Command (aka the 'Open Apple') key` and it works fine in FireFox, Chrome and Safari.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [19 September 2023 09:55 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/16 "2023-09-19T09:55:25Z")

</div>

> [@zenofmud](#):
>
> On the Mac it works fine but you need to use the

> [@Steve-Mcl](#):
>
> [Nodes : Node-RED](https://nodered.org/docs/user-guide/editor/workspace/nodes#quick-add-dialog)

OK got it, on 3.1.x you pull the wire and the menu pops up. On 3.0.2 you hold the command key, click on the workspace, add node _and_ connect the new node to the old (if cmd key is kept held). In 3.1.x that changes to I connect the old node to the _new_ node. I was using 3.1.x paradigm i.e. using an existing node to connect to a new node when that doesn't work in 3.0.2 (hence my acrobatics to try and get that working.)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [18 November 2023 09:55 UTC](https://discourse.nodered.org/t/link-call-nodes-visually-showing-the-connections-to-link-in-node/81396/17 "2023-11-18T09:55:50Z")

</div>

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