List of button references, or references that follow movement

[McMark1441]

Is this a feature relevant to companion itself, and not a specific module?

• I believe this to be a feature for companion, and is not specific to a module

Is there an existing issue for this?

• I have searched for similiar existing issues

Describe the feature

A feature that will let me see if a specific button is referenced in any other buttons or triggers.

Another tab/pop-up/other window inside the button editor that will list all the other buttons that references the selected button.
Or even just a Global list that can be searched and sorted.

Bonus Feature: Button references could be set as either static to a specific location, or they could follow the referenced button if it moves.

Usecases

This way if I ever move a button that is referenced somewhere else, things don’t break. The biggest issue is that anytime I want to rearrange or re-organize my pages, I have to do so very carefully. I have about 20-ish pages worth of buttons, and if I have to move one button, I have to go fix the references to that button in 5+ other buttons.

*Edit: Formatting

[thedist]

This would be particularly difficult to implement, as any action that references a button could be using variables, or expressions, which may be only evaluated at the time of execution. This would mean that any time you open a window that shows a list of references to that button Companion would have to first know which actions do things with buttons, and then parse the fields of each and every one of them which could potentially be hundreds or thousands of fields, and even then it would only have a list of which actions are referencing that button at the moment in time it was evaluated so could potentially be immediately stale and show actions that no longer reference that button, and would also not list any actions which don't currently reference that button but may at some points in time.

What I would suggest is perhaps consider better practice for your use case is to not use static references to buttons, so for example if you move a button rather than changing an unbound number of other things that could be referencing it you instead use a variable, and then change that variable when you move the button and if you have 1 button or 100 buttons that use that variable they would all be immediately updated. Depending on your needs you could even do things like using multiple variables, so if you change the page order you could just change a page variable and it updates all references for buttons across that entire page. There's several different ways to achieve better handling of button moves.