Quote: Well now we have broken formulas all over the place instead of just in C8-F18. There's only one broken value when I load the sheet but as soon as I start filling in stuff (especially what warp engine I'm using) formulae start breaking all over the place. Could be more of the indirects are broken, I don't know enough about spreadsheets to say.
*inscribes regular 17-gon*
*rattles abacus overhead*
charis, CHARIS,
CHARIS
I didn't know much about spreadsheet software ten days ago but I know a fair amount now. Enough to loathe kspread, anyway. The XLS export from Gnumeric may be weird, so I exported from oocalc and uploaded again. kspread, among other horrors, can't handle more than one argument to floor() and can't handle offset() at all requiring abuse of the indirect(address(row(),expr)) construct. Gnumeric and oocalc are both happy with the latest file. As I keep editing it I've added more formatting and validation which makes things happier here but may blow up in MSware.
For reasons I do not understand, a global replace of = with = may make broken formulas magically work; it worked here when importing gnumeric .xls into oocalc.
Kspread also had a problem with the construct: if (x>y; indirect(address(x-y;z)); 1), which I used for miniaturization since the miniaturization rates are table-lookup rather than algorithmic. It is possible bogusware will attempt to lookup (x-y;z) and barf when (x-y) is nonpositive. The workaround is indirect(address(if(x>y; x-y; 99);z)) with 100%s in O-P99. I find this inelegant, though, and if the formulas don't start broken I don't think this is the bug. Replacing = with = may shake the program into accepting the formulas. Or you could try
Third time lucky? spreadsheet
Thanks for bearing with me. I hope this spreadsheet will be useful even for non-Linux users.
Selentine