Request for Enhancement:
If you add something to a cell and don't press enter or click off the cell to save the cell, then you print, print will not pick up what is in the unsaved cell.
This is an "inconvenience to the user". I have twice now tried to figure out what the missing entry was in front of the bank teller on my deport slips. NOT FUN!
What I would see is something that would either
1) force a save if the print button was pressed (as does the "save" button), or
2) not allow you to print, as does Excel 2007. A "save your cell first" note would cut down on the confusion with this method, or
3) something cleaver that the programmer likes better.
Hmm can not confirm this on Windows builds, can already "print" with unsaved cells.
On Windows all the print actions--preview, print, preview in web browser--all pick up the cell/formula content from an 'unsaved' edit. Returning from that dialog will have triggered the save-needed actions (toolbar icon change, status bar icon change).
But, the Export actions (to PDF, JPEG, PNG, XHTML) drop the unsaved cell content.
So, guess could make a distinction between Export and Print depending on os/DE.
Windows 10 Home 64-bit en-US with
Version: 18.104.22.168 (x64)
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
I had initially though this was a bug, so I reported it over on
Bug 125895 - Calc: print does not print unsaved cell
Maybe there is something in the verbage over there that helps with this RFE
It would also be nice if every OS and export all acted the same
@Eike, should there be consistent handling here of uncommitted cells--i.e. 'no save' => no Print, no Export; or conversely 'save not needed' => will Print, will Export?
Seeing split capability as now, i.e. 'no save' will Print but won't Export, suggests things currently follow different paths.
Should be consistent, right? But then which action: 'notify a save required, and enforce' before any Print or Export; or 'allow' Print or Export including unsaved cell entries.
Seems some (print, export) do not close cell input before action, but others (save, saveas, print preview) do i.e. one ends up with the so far edited content being committed to the document. My take is that also print and export should close the pending cell input.
So issue accepted as a bug, removing UX.
I checked in
Build ID: 8d8f9dd80abf4e1eb08eee9763ea38f2b15f02b
and it gives an error if I try to export to PDF while editing a cell