🐛 Bug report | Cannot update job names after renaming fsm

[stevenlabelle]

Description:
If a fsm and its dependent jobs are renamed, the user cannot update the jobs field with the new names. Additionally, newly created jobs will still use the old name even if the user changes it.

Version:
Dev Version 3.0.0.23e43365b

Steps To Reproduce:

1. Create an fsm and run the model.
2. Close FBS.
3. Rename the fsm (e.g., renaming "FibPCLS_2D_5prestrain_1R_patchy_50E" to "FibPCLS_2D_5prestrain_1R_50E").
4. Rename the dependent files in the jobs directory accordingly (.feb, .log, .xplt)
5. Open the fsm in FBS.
6. The jobs entry in the model tree still displays the old name (this is expected).
7. The user can change the Name entry under Jobs>Info but not the files under Jobs>Properties.
   Additionally, if the user tries to run new jobs with the new name, they will still use the old name.
8. Change the Name under Jobs>Info (e.g., "FibPCLS_2D_5prestrain_1R_patchy_50E").
9. Select FEBio>Run.
10. Change the Job name entry to the new name.
11. Run the model. The output models will still use the original name despite changing Jobs>Info and the job name entry in the run FEBio prompt.

[stevenlabelle]

The expected behavior occurs if the job is deleted via right-clicking before running the model again. However there is no way to change which files existing jobs point to and the incorrect name is used for new files if old jobs are not removed.

[SteveMaas1978]

There are a few issues mentioned here, but going back to the original question, I added an option that I think will help. Now, when you open an fsm file where you renamed the job files, you can try the following: after opening the fsm file, try to open the feb file by clicking the little folder icon next to the file. You'll get an error message telling you that the file cannot be found, but then you also get an option to try to locate the file yourself. If you select yes, you get a file open dialog where you can pick the file that you want to associate with that job. (Remember to save the fsm file again.) Please give that a try and let me know if that addresses your first concern.

Regarding the other concern, I'm not sure if renaming the job (in the model tree) should also rename the files when you re-run that job. It's hard to know if that is really the intention of the user, and it's definitely not the recommended approach. If you want to create new files, it's always better to create a new job entirely.