[Feature] Improve "Rescript Message" for methods where the VI name has changed.

[qalldredge]

Summary / Description

If the method that is wrapped in the Do.vi has a different name than the message, rescript the message to the new name changing: the message class name, the send VI name, folder location on disk, and icons.

Motivation / Use Case

I had a customer change the desired name of a field in the UI. Although I could have just changed it in the UI and not the underlying code, it was a different enough change that it would be confusing for anyone (including myself in 6 months) inheriting the maintenance of the code. This caused methods and messages needing to be renamed.

Proposed Solution / Feature Details

Fix the "Rescript Message" to take into account the change in the name of the method in it's Do.vi and base everything off that. Also, cleanup orphaned folders the old message was in if empty after moving the message class.

Alternatives / Workarounds (optional)

Painful renaming and editing of icons.

Possible Implementation (optional)

No response

Additional Context (optional)

No response

[qalldredge]

Steering committee discussion:

Is this more a refactor of classes in general?
Do we need to handle concrete implementations when rescripting an abstract message in the interface?

Some conclusions: If not in memory, all bets are off.
Q just wants it to be smarter and look at the wrapped method in the do and base it off that. Concrete implementations would\could still be manual.

[dhooks01]

I think this is a great idea. The current workflow for renaming is bad.

There is a rabbit hole one could potentially go down if you tried to initiate the rename from the payload method. But even if the functionality could only be initiated from the existing message class, that would be very helpful.

[qalldredge]

I think this is a great idea. The current workflow for renaming is bad.

There is a rabbit hole one could potentially go down if you tried to initiate the rename from the payload method. But even if the functionality could only be initiated from the existing message class, that would be very helpful.

There already is "Rescript Message" functionality. I would just add to that. The steps are:

1. Find the method in Do.vi. (If no Do.vi or multiple methods found, fail or rescript as currently executing.)
2. Check if the method in Do.vi is renamed; if so, script the renaming of the classes, folders, send method, icons, etc.
3. If the method is not renamed, execute the rescript as written.

[niACS]

I think Sam Taggart may have a rescripting tool that does this. I've reached out to him for information.

This is enough of a pain point that it's worth pursuing.