When I send something into a pad and duplicate the pad in the document, a nice handy arrow is indicating that a value is going in elsewhere (if I get that right). This happens both for adaptive pads and pads that have a type set.
But when I connect something to the output of the duplicated pad (for example an IOBox), the arrow disappears.
Edit: changed to bug category
The Gray Book states here:
A little triangle above a Pad is a hint that there is a Pad with the same name in the patch that is also written to.
But this is still the case when I read from the pad (like in the second image), so why does the little triangle dissapear? It would actually be handy if it stayed there, if the pad is used in different parts of the patch, so you immediately see that somewhere else it is connected upstream.
Yes, looks like a bug, the triangle should always be there if it gets written somewhere else.
Coming back to this, is this a bug or is this behaviour intentional? It would be very handy if this was still visualized when connected downstream.
The arrow indicates that this pad is written somewhere else, reading that pad will NOT add this arrow, when tracking bugs regarding unexpected values, you only need to know whether the value can change somewhere else. Reading a pad will never change the value and is therefore safe.
If you want to see other usages, select it and press F3 several times. Another visualization of all the usages of a pad is still missing.
I am still referring to the case, when a pad is written to AND read from. It would be nice, if the arrow was not disappearing here.
But then again… probably like everything else a tricky one, because how to visualize multiple operations writing to a pad.
In my case the search comes up, probably not what you are referring to?