Ed, This has been a MAJOR grip of mine for years. Why would SW want to save something that has NOT changed. Just changing the configuration of a screw in an assembly causes SW to want to save the screw. The screw model DID NOT ACTUALLY CHANGE. Why would I want to re-save it.
However, if there was an actual change to a part that may not be obvious (such a in-context feature referencing another part that did change), then I want SW to show me a printable list of which parts it wants to save! Otherwise, I may actually miss the fact that part23 changed because I made changes to part14. Currently, in an assembly with lots of in-context relations, I have to KNOW these references of the assembly inside-out in order to figure out all of the parts that actually changed by manually making a change to one part. This can be very difficult and can increase the potential for user error. A simple popup while saving the assembly saying:
"hey buddy, since you changed part14, this caused changes in part23, part27, & part31. I am going to save them as well. OK?".
Ok,ok. Maybe not in so many words....