Revision tags: AOO417, AOO420-Dev-m1, AOO416, AOO416-RC1, AOO415, AOO414, AOO413, AOO4121, AOO412, SNAPSHOT, AOO411, AOO410, AOO410_Beta |
|
#
f431c806 |
| 20-Dec-2013 |
Jürgen Schmidt |
#123891# consolidate @since tag, in future only OpenOffice <version> git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1552560 13f79535-47bb-0310-9956-ffa450edef68
|
Revision tags: AOO401, AOO400 |
|
#
4f913391 |
| 05-Feb-2013 |
Ariel Constenla-Haile |
i119977 - Update version number to 4.0.0 git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1442743 13f79535-47bb-0310-9956-ffa450edef68
|
#
af1681ac |
| 07-Dec-2012 |
Ariel Constenla-Haile |
Fix build breaker: missing css::uno::XInterface include git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1418186 13f79535-47bb-0310-9956-ffa450edef68
|
#
74c4339d |
| 06-Dec-2012 |
Ariel Constenla-Haile |
#i121442# - API wrapping StatusBar functionality In the current implementation and its API design, it is impossible to implement a StatusbarController in UNO, because there is no way in
#i121442# - API wrapping StatusBar functionality In the current implementation and its API design, it is impossible to implement a StatusbarController in UNO, because there is no way in UNO for the controller to manipulate its status bar item; the current implementation of UNO based StatusbarController have to access directly the VCL StatusBar through the AWT XWindow in order to manipulate its item. Designing an API that wraps the VCL StatusBar does not make sense: a StatusbarController should only have access to the status bar item it controls, not the whole status bar. Therefore this new interface represents only the functionality of an item in a status bar, to be controlled by a StatusbarController. git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1417849 13f79535-47bb-0310-9956-ffa450edef68
show more ...
|