Issue 117188 - css.awt.grid.XMutableSortableGridDataModel: adding rows destroys the sorting, but still claims the data is sorted
Summary: css.awt.grid.XMutableSortableGridDataModel: adding rows destroys the sorting,...
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Solaris
: P3 Normal
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@api
Depends on:
Reported: 2011-03-03 12:10 UTC by Frank Schönheit
Modified: 2017-05-20 09:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

document to reproduce the bug case (14.26 KB, application/vnd.oasis.opendocument.text)
2011-04-01 10:58 UTC, Frank Schönheit
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2011-03-03 12:10:38 UTC
- open the attached document
- press the button to execute the contained macro which opens a dialog
  demonstrating a few of capabilities of the UNO grid control
- sort the data in the control by clicking onto a column header
- append a new data row by clicking the "Append Row" button
=> note that the row is indeed appended, so that effectively, the data i
   not sorted anymore. In contradiction to this, the column header still
   claims the data is sorted.

Either the sort indicator should implicitly be removed upon appending new rows, or the new rows should be inserted to the right position within the other rows, respecting the current column sort.
Comment 1 Frank Schönheit 2011-03-03 12:13:43 UTC
fixed in CWS gridfixes, by implicitly removing the sorting when new rows are added.
Comment 2 Frank Schönheit 2011-04-01 10:58:09 UTC
Created attachment 76244 [details]
document to reproduce the bug case
Comment 3 Frank Schönheit 2011-04-01 11:01:33 UTC
fs->msc: please verify in CWS gridfixes
Comment 4 marc.neumann 2011-04-05 13:25:21 UTC
verified in cws gridfixes
Comment 5 Oliver-Rainer Wittmann 2012-06-13 12:29:42 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
Comment 6 Li Lin Yi 2012-06-21 09:54:29 UTC
Veriried on trunk r1351249.