Skip to content

"Unsaved changes" detection is usually wrong #314

Description

@bgribble

Currently this works by serializing the patch state and string-comparing with the serialized load-file. Differences in object IDs generally throw this off.

Could this be done with a UI-side check of actions affecting state?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions