Logo Autocomputing
Call Support
Gridtop Beta Manual › Part VII: System › 36. Saving and Recovery

36Saving and Recovery

You never need to save your Gridtop. This chapter explains how it saves itself, where the copy is kept, and what happens when you leave.

36.1 Gridtop Saves Itself

Every change you make (a moved icon, a new connection, a window opened, a word typed) is saved within a second or two of your stopping. What is saved is your whole Gridtop: every object and connection, every window and where it is, docked, floating and broken-out panels, conversations, the Editor's tabs with any unsaved text, and the arrangement inside each folder and Workflow. Reload the page, and it comes back as it was.

Your files are a separate matter: they change only when you save them (23.5). Gridtop's saving keeps your workspace, and never overwrites a file. If a save cannot reach the server, Gridtop says so once, Could not save your Gridtop., and tries again with your next change.

36.2 The Recovery Copy

Your Gridtop is saved in two places at once: on the server, in a hidden folder of your drive, and in your browser. When you open your Gridtop, it loads whichever copy is newer, so if your connection dropped, or your computer stopped, before the last save reached the server, the browser's copy fills the gap the next time you open your Gridtop on that computer.

36.3 When You Leave

Close the tab, reload the page, or shut the computer down, and Gridtop saves what it can on the way out. Exit Gridtop (2.5) is the careful way to leave: it shows Saving…, waits until the save has reached the server, and only then closes.