Bug 65191 - EDITING: a cell with a formula (not only a number/string) go in blank after enter if autocalculate is off
Summary: EDITING: a cell with a formula (not only a number/string) go in blank after e...
Status: RESOLVED DUPLICATE of bug 66564
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.0.0.beta1
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-30 21:14 UTC by m_a_riosv
Modified: 2013-12-06 22:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m_a_riosv 2013-05-30 21:14:42 UTC
Win7x64Ultimate
Version: 4.1.0.0.beta1+
Build ID: d24df4c708b8eb8dc3689fa72cbfc4e02e97f6b

Open a new spreadsheet:

Disable Menu/Tools/Cell contents/Autocalculate

Enter in any cell

+2*1

Cell seems to be in blank.

Push F9 to calculate.

Cell value is showed.
Comment 1 Jorendc 2013-06-01 13:39:12 UTC
Thanks mariosv !

I can reproduce this one using Linux Mint 15 x64 with LibreOffice Version: 4.2.0.0.alpha0+ Build ID: 467d5e0a2e074ff2afb4d1b1a37cff2094b0895

Therefore I mark this one as NEW. Highest Blocker looks a bit overkill to me. IMO this should not block the release of 4.1. Iherefore I'm going to mark this as critical/high. I hope you agree with that?

@Markus: looks quite serious to me, as a calc-noob :). Any thoughts?

Kind regards,
Joren
Comment 2 Markus Mohrhard 2013-06-01 13:55:29 UTC
This is by design.
Comment 3 Kohei Yoshida 2013-10-14 22:48:54 UTC
Actually this is a bug, and I still see this with the latest master.

The '+' should have the same effect as '=', so if =2*1 and +2*1 behave differently, then something is fishy.  Also, when typing =2*1, even with the auto-recalc off, it should calculate when entered.
Comment 4 Kohei Yoshida 2013-10-14 22:49:13 UTC
Back to NEW.
Comment 5 Eike Rathke 2013-12-06 22:17:50 UTC

*** This bug has been marked as a duplicate of bug 66564 ***