Hi all,
Carsten Driesner escribió:
Paolo Mantovani schrieb:
Hi,
Carsten Driesner ha scritto:
[...]
Third (and last for now): com.sun.star.awt.UnoControlContainer and
com.sun.star.awt.UnoControlContainerModel go beyond my understanding,
although I've been using them so far this way
- instantiate both at the global service manager
- set the model at the control
- add the control to a parent XControlContainer
It turns out that the model can be instantiated at the dialog model's
XMultiServiceManager (obviously just because it supports
UnoControlModel), and then be inserted by name in the dialog model's
XNameContainer.
But when the control model is instantiated this way, there is no
control
at all: XControlContainer::getControl() at the UnoControlDialog returns
null.
The control is the "view" of the control model. If you insert a model
there is no view. The view will be created on demand when you call
execute() at XDialog.
Hi Paolo,
I didn't catch that we talk about the UnoControlContainerModel as a
"normal" control. It's simple, you cannot nest UnoControlContainerModel.
Although you can add it them into a container model, they won't do
anything useful.
anything useful? for doing complex AWT controls I was using the
technique they use in OOo Wizards (generally speaking ,
one-in-top-of-another-placing), but after reading Paolo's
BasicAddonBuilder source code, I started using his technique, which is
more powerful to me (by the way: thanks Paolo!)
Just take a look at what he achieves in his wizards, and you'll see that
they *CAN* do lots of useful things (at least in Paolo's hands)
Regards
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.ArielConstenlaHaile.com.ar/ooo/
"Aus der Kriegsschule des Lebens
- Was mich nicht umbringt,
macht mich härter."
Nietzsche Götzendämmerung, Sprüche und Pfeile, 8.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
