To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=98349


User tl changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'tl'
--------------------------------------------------------------------------------
             Assigned to|tl                        |jsc
--------------------------------------------------------------------------------
                  Status|STARTED                   |NEW
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Wed Feb 11 11:22:16 +0000 
2009 -------
It may be that this one can not be fixed since unfotunately WrapTextMode is an
enum. 

For C++ it will be ok to add an entry like (in pseudo code):
...
                THROUGH_TRANSPARENT = THROUGHT, 
...

That would just add another name to the enum *without* actually extending the 
enum.
But how about that in other languages like Java, Python, etc.?

tl->jsc: do our IDL files allow foe such a change?
If not we would be required to provide a whole new enum while keeping the old
ones as well for compatibility and that is completly out of question I believe.

BTW: the same problem (THROUGHT being used in API exists for other enums as 
well!)


---------------------------------------------------------------------
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]

Reply via email to