Closed Bug 501990 Opened 15 years ago Closed 15 years ago

save file before loading another one

Categories

(Skywriter Graveyard :: Editor, defect, P1)

Product:
Skywriter Graveyard
Component:
Editor
Version:
0.3.0
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: pederbl, Assigned: dion)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.33 Safari/530.5
Build Identifier: tip

details

Reproducible: Always

Steps to Reproduce:
1. make changes to a file a.txt
2. exec newfile command
3. -> All changes are now lost.
I noticed the same thing.  This bug is only in version 0.3.0
Confirming and moving to Editor.
Status: UNCONFIRMED → NEW
Component: General → Editor
Ever confirmed: true
OS: Windows XP → All
QA Contact: general → editor
Hardware: x86 → All
Version: unspecified → 0.3.0
This bug is present in tip; with collaboration off, switching files loses all changes.
Priority: -- → P1
Target Milestone: --- → 0.4.0
Let's solve this issue in 0.4 in the following way:

- When you switch files and you have unsaved changes, we automatically save those changes (this sucks, I know)

In a future release (0.4.x or 0.5), "collaboration" will always be on and changes will be persisted to the cloud, and you can save at will. If you lose connectivity in the middle of an edit session, the client will queue up the changes and send them to the cloud when connectivity is restored.

In a release after that, we'll address occasionally-connected scenarios.
Assignee: nobody → jwalker
Assignee: jwalker → dion
Autosave is implemented in changeset: 324fa3d5542c

Will open a new bug to discuss future changes.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.