Re: Editor Developers.....Do Something
I wholeheartedly agreed that a good UPS makes damn good sense.
I however suffer far more from Mr Gates version of a stable operating
system that Eastern Electricity's occasional spikes...
At the moment I am fiddling with an editor,
(Don't hold your breath, June/July is looking possible, all I'll say),
with reservations about this topic eloquently just voiced by Chris:
>I don't think it's good programming practice to rely on an autosave
>feature. I did try using it before, but found that it would save at
>inopportune times, sometimes overwriting work that I wasn't fully
>sure I wanted to be gone.
Absolutely agreed.
>A GOOD option to have would be an autosave feature that will only save
>if you haven't, within a set amout of time. EG. if you don't save within
>the half hour, autosave. Autosave should also save to a unique filename,
>not overwrite the original.
Hmmm. What name/what recovery? If you are editing fred.txt & after 35
minutes, the PC crashes, who/what knows what ~EMF037B.TMP holds after
you have rebooted?
I strongly believe you should have to hunt down the original, rather
than hunt down the most recent changes.
Thoughts on that please.
(full revision history is not practical just yet, sorry!)
Also, when/if you press F5 to run the application in a trial, can I
assume you are happy to have it saved?
(You can still undo the last 100 changes, provided the app doesn't
crash the PC, in which case tough)
Pete
|
Not Categorized, Please Help
|
|
