predictiple
commented
4 months ago One possible solution is to have separate Save and Run buttons. Save should work even if the VQL is incorrect. Often I have needed to go to another cell to copy a snippet while forgetting that I haven't yet run the current cell (because it was still incomplete/WIP), thus losing my changes.
An autosave of the current cell would be ideal.
Run should save&run as it currently does, but it should save even if execution is cancelled, as per OP.
Some of the button descriptions are also not accurate, for example this Undo doesn't actually undo anything. It should be labelled Cancel, consistent with the same button in the notebook toolbar.
scudette
misje
I've been caught off guard a number of times now that if my notebook cell has invalid syntax when executing, and I'm impatiently waiting for those handful of seconds necessary seconds for the "Edit cell" button to reappear, clicking the stop button destroys all my work since the last query execution. Can we keep the "unsaved" VQL even if it had a syntax error and the user pressed stopped instead of waiting for the edit button to appear again?