add save when verifyng and uploading #1934 #2214
Conversation
|
@ArduinoBot build this please |
matthijskooijman
added
Component: IDE user interface
|
My apologies if this is the wrong place for this, but I feel strongly about the importance of this feature. As an end user of the IDE, I'm baffled as to why this setting isn't default. Every other IDE I've used saves upon compiling. It may be the case that other IDEs had to save before compiling, and it's kind of neat in a technical kind of way that the Arduino IDE doesn't have to save first. But from an end user perspective it makes no sense. Modern UIs should be moving away from the entire idea of 'save' - which was born out of necessity in the days when hard disks were monumentally slow. Now with large memory caches and fast disks, we should be designing apps to save constantly. How often do you see 'Save' in a tablet or phone app? Hopefully never. For those that hate this idea, it's could be because your workflow is all wrong. We have Undo now, and have for quite a number of years. We are all using version control locally? So saving only at specific milestones, if and when you remember is not the way to work. OK, I've digressed a little. This change doesn't go as far as I'd like, but it's a start. Please, please add it to the 1.5.8 release... preferably as a default... but I'll take what I can get :) |
|
Hi @GregWoods a cloud-like automatic save needs the undo-redo history to be preserved after closing the IDE (and saved with the sketch maybe?). In principle I agree with you, but in practice your suggestion requires a certain amount of work to be done. In the meantime, to give you what you can get as soon as possible :-), you may try one of the builds here: those are test builds that have the auto-save feature implemented. Your feedback would be highly appreciated and eventually accelerate the adoption in the next release. |
|
@cmaglie - Thanks for taking the time to reply. I've already installed and used the test build. So far so good. I'm glad to see that save on verify is ON by default. |
|
Hi @fulvioieva . Your feature is good, but you have to write it in the way that if the file is in read only (example) it has to fail in a transparent way otherwise every time you modify it and click on verify or upload the message: the file is in read only.. and so only is displayed and this isn't very funny! |
|
@agdl First, the file should only save if it has changed. If it is trying to save an unchanged file, then this is a bug (sorry, I haven't tested this behaviour yet). |
|
@GregWoods my observation is based on the fact that very often I (and I think many others) start to write my sketches starting from an example (that are read only) and I save my work when it works reasonably; testing it on the board. To do so I have to make many uploads so every time the message will appear. You can say: well save your work so you don't have problem. But I think that a check on the file (if it is read only -> don't save) is a better solution. This is my opinion i don't want to diminish your work! |
|
@agdl Playing with the samples is a good case for verifying/uploading without saving. In this case you are correct... the popup message is too intrusive. It should be reserved for a manual save. It should however be made very clear in some other way that the file is read only - maybe space on the bottom status bar can be used. |
|
All suggestions have been implemented on #2433, please follow up there. |
this pull close #1934