[Scene] Propagate renumbering of retrieved variables when one of them is deleted

Feature requests
1

When you have several « retrieve last state » actions and use them in other steps, deleting one of the « retrieve last state » actions sometimes causes a shift in the numbering

2

I had to go through my previous votes again for this one ^^
It’s true that for a long scene it’s quickly annoying if you cut out a part.

3

Instead of propagating, why not have a field to give the variable a name so there are no more issues — it would be fixed by us?

4

@Prof_Techno not a fan of this option, it’s an additional configuration that doesn’t really make sense.

That said, it’s true that up until now we used a variable name that is specific to its position in the scene; nothing would prevent generating a variable name unrelated to the position in the scene.

5

I would lean towards a visible name for the front-end as it is now (it’s very handy for finding) and a UID (random?) for the back-end, and Gladys would rely on the UID for links (that might already be the case).
However, for the front-end, it would be good if the numbering were rebuilt when there is a deletion or an addition.

6

Anyway, visually I wasn’t suggesting changing the current behavior; the idea is that nothing changes.

7

I edited this old request to add the to-be-processed label, and perhaps a devt with AI could be undertaken…

8

Hi everyone!

This topic is now in development.

A PR has been opened to propagate the renumbering of scene variables when an action is deleted in a group:

Feel free to follow the PR, test (optional, especially for small requests) and give your feedback here if needed.