Show uses of operations in patch explorer

[sebescudie]

Hey hey,

CTRL+J shows where class operations are used.

Would it be possible to show that information as well in the patch explorer? Each operation could show how many times it’s being used, and potentially where, in a collapsed dropdown below the operation name?

Thanksss

[sebescudie]

In the same vein, it would be nice if process nodes could show in the Definition if/where they’re being used in the current application, kinda like CodeLens does in Visual Studio.

Artist’s rendition

There, it shows me that MyCoolNode is used three times. Clicking this info, it could show me a tooltip with the three places where this node is used, and clicking one of those would teleport me to it.

Right now, it’s extremely tedious to keep a large/long running installation clean because you end up having tons of outdated stuff and you cannot be sure what’s still used or not.

Cross-referencing these since they kinda relate to the same thing

Making the IDE more communicative

bonjour, one of the concerns I have with the IDE is that it feels rather inert when you look at it. nothing tells you at a glance what’s running or not, which nodes are eating your CPU, where data is flowing, where are the nulls, the big spread counts and so on and so forth. for complex projects/libraries, this makes debugging horribly tedious. you end up creating IOBoxes to monitor stuff all over the place, placing WriteLine here and there to know when/if something happens. the fact that you…

Clean/mark unused operations

hello there, when a class has many-many-many operations, and at some point some of them become useless, it’s really tedious to find out which can safely be deleted. maybe the left side menu could show if operations are used or not in the class so we could quickly get rid of them.

Thanks for considering!