To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=100252
------- Additional comments from billgradw...@openoffice.org Tue Mar 17 17:09:33 +0000 2009 ------- I can send you the spreadsheet (about 500K, 38 sheets) and all the passwords in it via your personal email, but as it contains financial info I don't want to post that. Also, This has to do with another issue I've noticed in the last several releases. If a cell is not visible on the screen at the moment, it does not get calculated. If you scroll the screen to make the cell appear it does indeed have the correct answer, but while it is not visible it has the answer from the previous time it was visible. This is patently absurd. I found the following which addresses the issue tangentially:"Calc: working with elements outside the visible area" on the ux-discuss site. I know this is the case because my macros read from cells that may or may not be visible depending on how the user currently has his display of the sheet set up. My macros do the same thing every time but depending on if the user has a cell visible or not creates different and sometimes incorrect output. Example - Cells A1 thru O42 are visible on the screen. Cell A50 contains a sum for A1 thru A49. When the user enters data in any visible A* cell, the total is NOT updated in A50. If a macro is executed to list what is in A50, it will not contain the correct information. If the user scrolls the screen down to make A50 visible, it will have the correct total. Executing the same macro now produces the correct answer. My macros read the contents of cells all over the place and not having a cell calc'd just because it doesn't happen to be visible to the user at the time makes no sense at all. The spreadsheet will produce different answers depending solely on how the user has his viewing screen set up at the time. That's not a bug, but a major design flaw that renders the app unreliable in the extreme. My spreadsheet is a Point of Sale system I wrote for my wife's restaurant. We were giving meals away because the totals weren't correct simply due to how my wife happened to have the viewing screen set up. If she scrolled down to where the meal totals were, and then printed an invoice all was well. If she didn't "see" the total and simply hit the invoice button, the invoice would be short. I wanted to add this real world comment to show that not calcing cells that just happen to be invisible at the moment is blatantly wrong, as giving away meals solely because of how the screen is set up is wrong. Forcing a recalc of the entire spreadsheet is NOT the answer as that slows things down too much and OO Calc is already pretty slow. The correct thing to do is to follow the chain of dependant cells and update all of them regardless of their current visibility. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@sc.openoffice.org For additional commands, e-mail: issues-h...@sc.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
