saikyun / freja

Self-modifiable editor for coding graphical things
66 stars 2 forks source link

Behavior for quitting #5

Closed sogaiu closed 3 years ago

sogaiu commented 3 years ago

May be it would be nice to confirm quitting if there are unsaved changes?

saikyun commented 3 years ago

I wonder what approach might make most sense. Perhaps a good old popup is fine.

sogaiu commented 3 years ago

If that's the simplest thing to do and nothing else comes about, may be it's good enough?

Perhaps It's the kind of thing that could be replaced later without significant consequences.

saikyun commented 3 years ago

Yeah, it would be a pretty surface level thing. :)

saikyun commented 3 years ago

So far new checkpoint system seems to be working well. https://github.com/saikyun/freja-checkpoints Main missing part is behaviour when starting freja without a file as input, and that opening files seem to act strange atm. Will keep working on those issues.

saikyun commented 3 years ago

Now a scratch file is created and opened when starting freja. Will need to test freja-checkpoints on windows too though, since now linux setup is assumed.

Need to fix opening files, then it should be done for linux.

saikyun commented 3 years ago

Oh, and I need to store a checkpoint when opening a file too. Right now it's possible to open a file with no checkpoints, make changes, and be unable to go back.

saikyun commented 3 years ago

Fixed the above. Now I just need to move this stuff into regular freja instead of relying on user to include in init.janet.

saikyun commented 3 years ago

Now added to freja properly.