Description: There's an apparent bug which, when a Calc document is open, tries to convert an existing txt file to a Calc document rather than open it. Steps to Reproduce: 1. Create and save a txt file 2. Open an existing Calc document 3. Go to File > Open Recent and select the txt file 4. LO opens the Convert to Calc document dialogue Actual Results: I'm either forced to convert the txt or to abandon. Other formats (e.g. odt Writer document) don't seem to be affected and open normally in the format they are saved in. Expected Results: If I open an existing txt via Open Recent, I do not expect to be forced into a Convert dialogue without even an option to abort the import. Reproducible: Always User Profile Reset: No Additional Info: n/a
This is correct behavior and by design. You are working in Calc, a text document is not ODF and will receive the module specific handling which with Calc is to take it through the 'Text import...' filter dialog. If you need a Text document (from a Writer session) to stay a text document and be opened by Writer--shift your active LO module to Writer. Or, save the text document to ODF, i.e. .odt
Errrr that's bizarre and hardly obvious to any end user who wasn't involved in writing the code. At the very least I'd expect to see some sort of over-ride in the UI offering to "Open as txt instead"
(In reply to Michael Bauer from comment #2) > Errrr that's bizarre and hardly obvious to any end user who wasn't involved > in writing the code. At the very least I'd expect to see some sort of > over-ride in the UI offering to "Open as txt instead" Makes perfect sense if you think about folks working with delimited text (CSV,TSV etc.) in a file with a .txt extension. Having import behave based on active LO module is very efficient filtering. Rename/reformat the text file to ODF compliant, or when needing to open text shift to WRiter (use an existing session or just open wtih File -> New).