Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How about ACTUALLY saving? #2

Open
Pontiac76 opened this issue Feb 12, 2023 · 1 comment
Open

How about ACTUALLY saving? #2

Pontiac76 opened this issue Feb 12, 2023 · 1 comment

Comments

@Pontiac76
Copy link
Owner

#1 needs to be completed before implementing ACTUAL saving of files.

When the user hits File>Save the current history of edits and generation are saved.

The format of the save I'm not quite sure about yet. I've not toyed with saving the objects (tStringLists) to a tStream yet, but I have SQLite code that I've used for years. Lazarus has built in functionality for SQLite as well but I've not used their methodology yet. Not sure which way to go yet.

@Pontiac76
Copy link
Owner Author

I've got a resemblance of saving to a SQLite3 file, but running into conflicts when using the TheCode.Modified property.

I'm attempting to avoid saving every version every time you hit CTRL-S, so maybe something along the lines of doing a comparison between what is in the editor and what the last save would have contained, and decide based on that for the actual save.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant