Blueprint marked as Changed without actually changing anything

Thanks for your answer, but I still don’t understand…
When you are using code, if you open a class without changing anything, the file is not marked as changed.
When you are using code, if you modify a class referenced in another one, this last class file is not marked as changed.
When you are using code, if you change a mother class, the children class files are not marked as changed, even though obviously their behaviour are modified.

What I’m waiting from the BP system is to behave like if I was coding. Because even if I am aware that a guy in the team is working on a BP, how can I check its content, how it works etc, without opening it and thus marked it as changed ?

And what is bugging me even more is the fact that if I close the editor with BPs marked as changed for one if the reason explained above and without saving anything (reverting eventual changes made to this BPs) and the open the editor again, everything will work fine. So I wonder “what are those changes that made the editor mark my BPs as changed ?”