Unsaved Changes - subviewS

After compiling test harnesses, saving and closing, the test model synchronizes and all referenced subsystems containing state charts or truth tables have unsaved changes.

Using the Comparison tool it says there are non-functional changes subviewS

Has someone encountered this problem or knows a workaround for this?

Answer 1

[Guilherme Costa Nascimento]

"subviewS" is an internal parameter related to Stateflow that is being incorrectly picked up by the comparison tool. It's non-functional, so you can safely ignore differences coming from this.

Starting in R2025a, this parameter is correctly handled by the comparison tool, so you can either upgrade to R2025a or a later release, or at least hide non-functional parameters when comparing models.

[Nino]

Hi Guilherme,

thanks for the response.

I've been told at a mathworks webinar that this issue is resolved from 2025a on, but I thought there might be some additional settings to prevent these "unsaved changes" also with 24b or maybe some creative solution of a user of which I haven't thought of yet...