No, I found the old plotter just a convenient display that confirmed what was going on rather than being concerned about measurements etc. Yes I use a scope on the real thing at home so no concerns but felt like it was still a useful feature.
The old plotter had many limitations.
Perhaps removing it was premature, but you can still use the oscope as a plotter in 0.4.14-SR4: the main limitation is there are only 2 channels, and some bugs.
The new oscope still lakcs some features, but it is not finished, and you will be able to do anything you did in the old plotter and much more.
Still trying to figure out the editor saving thing
It is basically:
Every time you compile the file is saved if it was modified.
When you upload, file is compiled if it was modified (so also saved), if not it uploads the old version.
As far as I know almost any compiler read files from disk.
Some IDEs may create a copy and compile from that copy, but in general files must be in disk to be compiled, because most IDEs invoke external compilers as command line.
Arduino IDE, for example create a copy anyway, because it is not compiling the skecth you write directly.
Most IDEs I know have an option to save files before compiling or not, but will compile what is saved to disk.
For example in Qt Creator if you don't save, then changes will not be compiled, so there is no way to test changes without saving.
I understand your point and that would be a nice feature.
Perhaps in the future it will be implemented, but it will require some stuff to be implemented before so the editor knows which files belong to the project.
I could add an option to save file before compiling or not, but then changes will not be compiled, so I don't see the point in doing it.