Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
Any way to get Autosave working????
I've lost work twice thanks to processing crashes... the ease of hitting cmd-R makes me for get to hit cmd-S, and then I suspend, and sometimes processing is just out to lunch when I come back. Is there anyway to make it so cmd-R autosaves?
Answers
It seems so weird that switch to js forces a save, and requires typing in a filename, but then I could be editing something (that I've clearly given a filename!) and run it and run it then processing dies and I lose all my changes.
which operating system are you using?
i'm on linux. and processing 1.5.1. if i create a sketch and run it (without saving it) i get a temporary file in /tmp/sketch_nov01[random_hex_digits]temp called sketch_nov01a.java which is the pre-processed version of my sketch with all the java bits added to it, but still recognisably my sketch.
windows and mac will probably do something. so even if processing crashes there is a chance that you can retrieve your code.
that said, losing work because you haven't saved it is the 'dog ate my homework' of programming problems.
This is OSX. I recreated the work since then.
In a normal programming environment, I'd agree that it'd be more Dog Ate My Homework. But I was doing many, many successful iteration runs on my commute home - by hitting cmd-r. And then, in a hurry to jump off the train, I just shut my lid. When it restarted, Processing was beachballing like mad.
I have a totally untested theory that it's caused by it working in a Dropbox folder, and so Dropbox changes out some stuff from under it and it becomes confused. But that's just a wild guess.
I've been trying to be more mindful with a double cmd-s, cmd-r. (Or when I'm in processing.js mode, I'm more compelled to save a lot., since it's cmd-s, switch app, cmd-r (for reload)). But I think it's a UI fail to have the default be "make all the changes and run you want! We'll probably remember to prompt you to save later"
I run lot of sketches (often copy / pasted from this forum) without ever saving them. That's one of the nice things in Processing!
When I do serious stuff, I save it, and I just have the habit to hit Ctrl+S often, not only before runs.
Well, it does save the code somewhere in the tmp dir for compilation anyway, so that's a way to salvage it.