About notes not moving when data are sorted.
Actually, I would not say that notes are "lost". They are still related
with their original cells, but when you want to see them, it is an
incredible mess to follow the arrow, discover the note and maybe place
it on its new place.
No solution (for simplifying the use of the spreadsheet)?
Marc Hug
[EMAIL PROTECTED] a écrit :
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=59745
------- Additional comments from [EMAIL PROTECTED] Mon Dec 17 05:32:52 +0000
2007 -------
A comment on the bug,
issues this bug causes,
and a workaround that works
(with some issues)
but breaks my mother's heart when I use it.
1. It is the same issue as 80174, 63671, 67076 and 61253
where the same thing happens on adding rows/cols, resizing rows etc.
Notes are being tied to an absolute position
(that of a particular cell that was once-upon-a-time near the 'noted' cell )
rather than a position always relative to the 'noted' cell.
2. It is especially egregious for finance and accounting use.
For example, at the beginning of every year finance people may add 14 more
columns (12 new months, year and budget)
to large spreadsheets. Almost all cells have notes
and all notes are effectively lost as they are so far off screen they are not
viewable.
For this reason I am casting 3 of the 5 votes I was given on registering,
for this bug.
3. A workaround:
(which feels a bit like mentioning the name of Lord Voldemoort
and offered slightly tongue-in-cheek), is:
before adding rows or columns,
close the spreadsheet, open it in Excel,
add the rows or columns in Excel, then close it again and continue work in OOO.
Notes are handled properly,
ie positioned relative to the 'noted' cell, in Excel.
It is not perfect, as not all formats are transcribed perfectly,
but it is better than losing access to the notes.
Of course if you don't have access to excel...
4. The argument above that this bug is really an 'enhancement'
because the present behavior is as per specification
is simply an argument that the bug is in the specification
not in the coding.
I think both specification and coding issues ought be addressed here.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
