Apache OpenOffice (AOO) Bugzilla – Issue 13672
ROW() fails in conditional formatting
Last modified: 2005-02-15 11:25:24 UTC
A common Excel trick to produce row banding is to apply conditional formatting as follows: set condition 'formula is' to '=MOD(ROW(),2)=0' and formatting to any colour background. This can be reproduced in OpenOffice Calc, however my tests revealed a bug. First I created a cell style called 'shaded' which had a colour background. I applied this conditional formatting to a column range of cells: 'formula is' 'MOD(ROW();2)', cell style = shaded. This failed; the column range of cells *was not* banded as expected. ROW() should be returning the row of the cell in which the formula resides -- as stated in the manual -- however, it appears not to be doing so. On the other hand, if I apply the conditional formatting 'formula is' 'MOD(ROW (A1);2)' to cell A1, and then I copy that cell to the range A2:A10, the column range is now banded as expected. The problem appears to lie with not specifying a specific cell reference for the ROW function. If I apply the cell values '=ROW()' to a column range of cells, this correctly reports the cells' row values, e.g. 1,2,3,4,5... so the row function is working correctly in that context.
Hi, this is not a bug. It works as designed. But I set the flags for an enhancement request. Bettina, 1 4 u. Frank
When fixed, this will provide a work-around for bug 25213.
When I try to use a formula such as =MOD(ROW(),2)=0 cpu usage jumps to 95% and stays there. version: win32 1.1.1b
I have just tested the banding function in Calc build 1.9.65. To recap: >> I applied this conditional formatting to a column range of cells: 'formula is' 'MOD(ROW();2)', cell style = shaded. This failed; When this conditional formatting value is applied to cells, it now works as expected. Cell banding (or any form of alternate-row formatting) now works just like Excel. For my part, this bug/enhancement is closed. However jminne might wish to follow up on his/her comments.
fixed with issue 34474 *** This issue has been marked as a duplicate of 34474 ***
double -> closed