joint motion triggers save file?

[didjital-shurco]

This happens to me all the time.  For example, I have a file with two components.  There is a slider joint between the two parts with a max, min, and rest value.  I save the file.  Then, every time I move the joint to show the motion and let it snap back to the rest position it triggers me to save the file.  Is there a way to disable this?  Since I have a rest position defined, the position of the components has not changed from the previous save version.  I don't like to leave my projects unsaved, but I also don't want to end up at version 3000 because I have showed to motion to colleagues in the office.

[jeff_strater]

I assume that when you say "it triggers me to save the file" that this happens when you close the design.  Is that correct?  If so, this is expected behavior.  Though you are correct that functionally the model is unchanged, in Fusion, there is no checking that you have executed essentially a no-op.  It just sees that components have been moved, and that is a model-dirtying change, so you would be prompted to save on close.

[didjital-shurco]

It does ask on close, but I was more referring to when its just open in fusion.... it will put an asterisk after file name showing it needs to be saved.  I would love for the asterisk to only appear when an ACTUAL change has occurred.  I often have 10 or more projects open at a time and constantly switch between them.  I like to keep projects in a saved condition in case of computer crash or power outage, etc.  I don't want to NOT save it, because as I switch between projects I cant always remember the state of each file.  So I save.... and I end up with version 937(!) by the time I am done...

It would be nice to be able to switch this behavior off to prevent this problem.

[jeff_strater]

I understand the desire, however, detecting that "no real change has happened" is a very difficult problem.  It requires a comprehensive before/after comparison of the entire state of the model.  For instance, adding a feature, then subsequently deleting it is essentially preserving the model state.  Even Word, whose data model is orders of magnitude simpler, cannot do that level of change detection.  Sorry not to have a better answer, but in all honesty, this is not likely to ever happen.

[didjital-shurco]

How about a checkbox next to each joint in the file tree that allows you to ignore it for model dirtying behavior?  That may be a simple solution right?