Configure Simulink to ask for new model version when saving the model

8 次查看（过去 30 天）
Ansh Gandhi
Ansh Gandhi 2020-10-16
评论： Ansh Gandhi 2020-11-3
Currently, Simulink can be configured to prompt for a comment each time a model is saved.
I do not want it to increment the version number on its own, so I have removed the AutoIncrement macro in the History section of Model properties.
Although, I would like to have the option of choosing the model version number along with the message each time when saving the model if possible so as to increment both major and minor releases at my own pace, conveniently, and without forgetting.
Currently using MATLAB 2017b
Thanks for the help!

请先登录，再回答此问题。

采纳的回答

Urmila Rajpurohith
Urmila Rajpurohith 2020-11-3
This might be possible using model callbacks, but it would have to be added to every model manually, or to the default Simulink template.
EX:
open the model
set_param(bdroot, 'presavefcn', 'str=inputdlg;set_param(bdroot, ''ModelVersionFormat'', str{1})')

更多回答（1 个）

Urmila Rajpurohith
Urmila Rajpurohith 2020-10-23
Hi
If you want to change the model version you can use "set_param" function before saving the model.
for example if you want to change the model version to 1.10, then you can use
set_param(modelname,'Modelversionformat','1.10')
Hope this helps!
  3 个评论
显示 1更早的评论
Urmila Rajpurohith
Urmila Rajpurohith 2020-10-30
Hi
Can you tell us more details about why you require this workflow?
because many people would use source control tool features to do this kind of tracking rather than depending on the user typing in information on each model save.
Ansh Gandhi
Ansh Gandhi 2020-11-2
编辑：Ansh Gandhi 2020-11-2
Hi,
I understand what you mean, in this case this workflow seems important in order to align all modelling activities and versions across different teams according to common release naming standards for major and minor versions. The documentation of the models need to be tied to SW version so having the model version number same as SW version number seemed like a good idea. Then the user needs to remember to update the major version of the model which maybe this prompt could help with. Commit ids and version control have been useful in the past, but documentation seems to be coupled more with model version number rather than commit id, which is more human readable as well.
I hope that made sense!

请先登录，再进行评论。

类别

在 Help Center 和 File Exchange 中查找有关 Programmatic Model Editing 的更多信息

标签

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by