Created attachment 68626 [details]
view of the sorting list
Can't add several sorting list (efficient in 3.5)
Created attachment 68682 [details]
View of the sorting list
Replaced attached TIFF image by copy in PNG format (easier to view and handle with most web browsers)
Thank you for your bug report!
I can partially REPRODUCE this problem with LibreOffice 184.108.40.206 on Mac OS X 10.6.8 (Intel).
Of couse, I *can* add new sort lists: open the options pane at “Preferences > LibreOffice Calc > Sorting lists” and click on “New”, then enter the comma-separated list in the right colum (“Entries”), then click “Add”, and then click “New” again to add one more sort list ...
But when I *close* the “Options” dialog window and open it again, my new list(s) are not listed anymore, they are gone.
So, I would state that the problem is “New Calc sort lists are lost after closing the Options window”.
Do you see the same?
Or does bug 53870 (see
describe your problem correctly?
Please answer (by coming back to this page:
and adding an additional comment), then we can proceed with this bug!
Thank you in advance!
(Internal QA hint: This is more or less a DUP of bug 53870, but there are some differences, therefore I want to clarify them first before marking this as a duplicate of bug 53870.)
*** This bug has been marked as a duplicate of bug 53870 ***
I aggree with you but
I guess there are two problems:
The one you discribe, (first sorting list you add is destroyed when you add a new sorting list)
LibreOffice sorting lists are not visible when you open option pane "Preferences > LibreOffice Calc > Sorting lists even they are present.
You are right, at least at the surface there are two problems. But I hope that Markus Mohrhard’s patch for bug 53870 has fixed them both (it is possible that both problems had the same reason in the code).
So I propose:
* let’s wait until there is a new daily build including Markus’ patch,
which was committed 2012-10-17 13:53:26 (GMT)
(at the moment, daily builds are not coming daily ;-);
* then we (I) can test if both problems mentioned by you are fixed now;
* if yes, this (your) bug report is rightly marked as a duplicate of
bug 53870, and does not need any further treatment;
* if no, we can always open your bug report again,
or, even better (Markus will probably prefer this!),
file a new bug report exactly for the remaining problem.
I have checked this issue again with a new master build:
LOdev 220.127.116.11.alpha0+ (Build ID: 370m0(Build:0);
pull time: 2012-10-21 10:01:47),
and as far as I can tell the problem is fixed. This result confirms that the present issue was really the same bug as bug 53870, so no more action is necessary.