Bug 60947 - FORMATTING: wrong format (negative in red) after reopening a file
Summary: FORMATTING: wrong format (negative in red) after reopening a file
Status: RESOLVED DUPLICATE of bug 60215
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Keywords: regression
Depends on:
Reported: 2013-02-16 09:15 UTC by stefan.linke
Modified: 2013-12-15 23:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

document as descibed above (7.13 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-02-16 09:15 UTC, stefan.linke

Note You need to log in before you can comment on or make changes to this bug.
Description stefan.linke 2013-02-16 09:15:54 UTC
Created attachment 74926 [details]
document as descibed above

Problem description: 

FORMATTING: calculated negative numbers are not shown in red colour when reopening a file

Steps to reproduce:
1. New document
2. fill cell a1 with -2, b1 with -1 and c1 with formula =a1+b1 (result: -3)
3. format all three cells as format of number with "negative in red"; all thre cells are shown in red
4. save the file and close libre office
5. open the file again: only cell a1 and b1 are shown in red, c1 is shown black

Current behavior:
see above

Expected behavior:
after reopening the file all three cells should be shown in red
Operating System: Windows 7
Version: release
Last worked in: release
Comment 1 Jorendc 2013-02-16 15:05:23 UTC
altered the summary a bit 'format' -> 'conditional format'
Comment 2 Jorendc 2013-02-16 16:07:23 UTC
Sorry, you are right. This isn't conditional formatting. My bad

I can confirm this behavior using LibreOffice Version (Build ID: c16e9f4ed97f65357e9986f46ad88ee9f223799) (build today) Linux Mint 14 x64. When you do ctrl+shift+F9 (=recalculation) this'll solve the problem.
Comment 3 Jorendc 2013-02-16 16:07:59 UTC
Thanks to Markus (=developer) I mark this bug as duplicate of Bug 60215

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