Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | sorting of rows goes wrong when references are present | ||||||
---|---|---|---|---|---|---|---|
Product: | Calc | Reporter: | dick_kaas <dick> | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | CONFIRMED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues, kami911 | ||||
Version: | OOo 2.2.1 | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | Windows Server 2003 | ||||||
Issue Type: | FEATURE | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
dick_kaas
2007-09-07 10:04:54 UTC
Hi, if the sorted range does not contain the linked (to) cells, just use absolute addressing. If the sorted range contain the linked (to) cells, how should this work ? Please attach a document showing your problem. Frank Created attachment 48057 [details]
test file wich demonstrates the error. just sort on sort_val
Hi, as I've said before, how should this work ? It's not just a few rows/columns to sort but could the thousands of cells in case you have to sort a whole sheet it goes into 16 Million cells. So the amount of memory would be huge if this is at all possible. But let's requirements decide. Frank May I suggest the following. I agree that the solution is not simple but first things an open source party should do is - admit that there is an error and - signal the user that something can go wrong second working on the solution. Well I like the get to the result answer. First - keep track of all the changes in rows/columns and do the sorting (looks like current method) [at least if you signal that there is a problem] This can be hardly a memory problem. - second check all the cells and make (on a base of changes) correct references. Talking about millions of transactions is a theoretical possibility and I donot think that that will occur in practice Think of what you can do better than Microsoft!! Dick *** Issue 82015 has been marked as a duplicate of this issue. *** *** Issue 93886 has been marked as a duplicate of this issue. *** *** Issue 85147 has been marked as a duplicate of this issue. *** |