Is your task related to a problem? Please describe.
When a model has an old SAMM version a migrator will start upon AME start.
However, some errors can prevent a model from being migrated.
In this case, if a user does not act accordingly, the model will remain unmigrated and the same process will begin whenever AME is started. This can be undesired:
As a user I may not care about this aspect model
As a user I may not be able to fix the aspect model in a previous AME version as suggested (or may find this process of reinstalling twice too cumbersome
Describe the solution you'd like
To improve the convenience I have these ideas:
Tell users to copy the list of nonmigratables to a text editor via clipboard (requires a copy to clipboard button)
Tell users that they can fix/delete them manually in the workspace UI (for that the copy to clipboard action before is used to remember the list of files if it is several ones)
Offer that the models can be deleted/archived: sent to an archive folder part of the workspace where migration won't be triggered. Also, for every file, the exact path (for copying to clipboard) is given as a reference. User choice after migration is "[Archive nonmigratables] [Dismiss]", and after migrating the list of exact paths is given once more with a copy to clipboard button so that I can still handle the archived models if I wish
Is your task related to a problem? Please describe. When a model has an old SAMM version a migrator will start upon AME start. However, some errors can prevent a model from being migrated. In this case, if a user does not act accordingly, the model will remain unmigrated and the same process will begin whenever AME is started. This can be undesired:
Describe the solution you'd like To improve the convenience I have these ideas:
Additional context Found on AME 5.1.1