Thanks Malte for replying. I had seen the implementation of "ErrorBox" class in OO 2.0 sources and thought
that XMessageBox is just a wrapper over it(including over InfoBox).
Regarding AWT, this concerns me a lot. If AWT is going to be
deprecated/reworked, then are we going to keep the
interfaces same. Or you mean things would be completely revamped (scary
scenario). Why is then the OO 2.0 SDK only supporting AWT? I would have
wanted touch VCL directly myself, but since it is not part of SDK (and
part of OO 2.0 source code), ended up using AWT. And OO developer's
guide is silent on VCL.
And looking at ErrorBox in OO 2.0 sources, based on the string length,
its width automatically increases. No one specifies the width, but just
the resource string. So, I think there is some width adjustment code
present.
- [ui-dev] Internalization Support for awt, and why is XMes... Aditya Pandey
- Re: [ui-dev] Internalization Support for awt, and wh... Malte Timmermann
- Re: [ui-dev] Internalization Support for awt, an... Aditya Pandey
- Re: [ui-dev] Internalization Support for awt, and wh... Malte Timmermann
- Re: [ui-dev] Internalization Support for awt, an... Aditya Pandey
- Re: [ui-dev] Internalization Support for awt, and wh... Malte Timmermann
