Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Ease text recreation after an application crash Apps
This is pretty simple, but I do it often enough that others may find it useful.

I develop digital audio using object oriented coding. It's pretty easy to lock up an experiment, and I dread having to reconstruct the recent changes I've made. Of course, you should save often, but I sometimes forget.

When this happens a force quit, and loss of all recent changes is my only choice. But I can at least save some time by switching to the finder and taking a snapshot of the window I was working on. Force quitting discards any changes, but at least I can see and retype the recent changes from the snapshot rather than trying to remember them.
    •    
  • Currently 1.67 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (3 votes cast)
 
[4,269 views]  

Ease text recreation after an application crash | 3 comments | Create New Account
Click here to return to the 'Ease text recreation after an application crash' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Ease text recreation after an application crash
Authored by: sjmills on Jan 10, '08 06:09:23PM

Good gravy. If you're working in Xcode, you really should just turn on the Save Before Build pref and save your from hours of grief or taking screenshots. It only makes sense. I wouldn't work in Xcode without it.



[ Reply to This | # ]
Ease text recreation after an application crash
Authored by: Pyrrhus on Jan 11, '08 07:19:52AM

Gee, I know this trick since OS 9 at least... Good thing it's public now!



[ Reply to This | # ]
Ease text recreation after an application crash
Authored by: dcottle on Jan 15, '08 09:41:35AM

Yeah, I've been doing it a long time too. Just thought I'd put it up. A lot of hints here are technical and specific. I love reading about simple tricks for better work flow.

I'm working in SuperCollider, which doesn't have an automatic timed save preference or save before build (run, in this case). You develop instructions for playback then launch it. Very little protection (maybe it should be added), so it's easy to lock up.

Of course, the real solution is the habit of saving before running, but I always forget.



[ Reply to This | # ]