Opening a file immediately marks it as having unsaved changes

[LarsKemmann]

This also triggers the "Project has unsaved changes" dialog on close.

Opening a file should not result in any unsaved changes until I actually make some kind of change to the file.

[countincognito]

This will always happen if auto-compile is on. The compilation output is part of the project file, so a recompile automatically updates the project file. If you disable auto-compilation, then it will remain unchanged.

[LarsKemmann]

I guess what I'm saying is that if the project compilation output is unchanged from the previous compilation, that should not result in the 'unsaved changes' triggering. I can appreciate that a check like that could require a bit of CPU time, but it would only ever need to happen once, when the file is first opened (or maybe if it's ever possible to implement undo/redo support, down the road).

[LarsKemmann]

@countincognito Let me know if you'd consider reopening this based on my comment above.

[countincognito]

I think I found a way to make this work. It should be completed in the next release.

[LarsKemmann]

This is fantastic!!! 🥳❤️