To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113636
User sb changed the following:
What |Old value |New value
================================================================================
Assigned to|sb |cd
--------------------------------------------------------------------------------
------- Additional comments from s...@openoffice.org Mon Aug 9 08:30:00 +0000
2010 -------
In what order configmgr reports set members to client code is unspecified. (It
looks like old implementation reported in the order found in .xcu file. New
implementation internally uses std::map, so happens to report lexicographically
sorted on Unicode values.)
Thus, while switching from "m1", ..., "m11" to "m01", ..., "m11" will appear to
solve the problem for now, it obviously does not really do so -- if internal
details of configmgr change in the future, the results may be garbled again.
So, what is really needed is to encode the entry order at a higher level
protocol than configmgr's API. (For example, in the menu code, sort the
elements based on their names or on an additional property.) Or am I missing
something?
---------------------------------------------------------------------
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...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
