Hi Frank,
Frank Schönheit - Sun Microsystems Germany escribió:
I will also try to get rid of the ghost base control by finding my own
LogicToPixel algorithm
FYI: A member of our team, Lars Langhans, who currently re-works the
report wizard to create SRB-compatible reports, needed
LogicToPixel/PixelToLogic functionality (in UNO) for this purpose. We
thought the fast way to get the UNO API for this was to implement it
ourselves, so we Just Did It. So, chances are you get something like
this in 3.0.
you mean all OutputDevice::PixelToLogic and OutputDevice::LogicToPixel
methods in vcl/source/gdi/outmap.cxx are gonna be wrapped in a new UNO
interface?
That's nice!
[Extra Toolkit explanation for those not familiar: the FrameControl
-strangely not in the awt module, but in the frame- is one of those that
can not be instantiated by the UnoControlDialogModel's
XMultiServiceFactory, set its model's properties (Height and Width in
MAP), and insert it in the model's container; in fact, it has no model,
it has to be created by the global service manager and added to the
XControlContainer of the dialog (NOT the dialog model's XNameContainer),
and the position and size must be set in pixels, not MAP, using the
control's XWindow::setPosSize() ]
Somewhat strange, especially the inconsistency with respect to the
non/existing model. But that might be only me - if it works, fine :)
I also find inconsistence the fact that some controls/models have to be
instantiated by the global service manager, instead of the
UnoControlDialogModel's XMultiServiceManager; besides that this isn't
documented anywhere: nor in the services IDL, nor in the brand new GUI
chap. in the Dev's Guide; so how do you know how to instantiate them ?
by try and error.
Little story about how I discovered the FrameControl (illustrating also
how bad- / un-documented can OOo API be): re-writing the GUI examples in
the SDK, I study the AWT controls once again. As I failed completely
trying to instantiate the
UnoControlSimpleAnimation / UnoControlSimpleAnimationModel
UnoControlThrobber/ UnoControlThrobberModel
controls I've never tried before, I did some introspection with the
UnoControlDialogModel and the XMultiComponentFactory, as result I've
found that the IDL was wrong (right: UnoSimpleAnimationControl/Model and
UnoThrobberControl/Model), and discovered this FrameControl in the
XMultiComponentFactory available services (and that the very important
property "LoaderArguments" is undocumented :-(
http://www.openoffice.org/issues/show_bug.cgi?id=86418)
Final warning for anyone reading this, and willing to try this controls:
the UnoSimpleAnimationControl crashes OOo! so be careful.
http://www.openoffice.org/issues/show_bug.cgi?id=86416
To see the glass half full and not half empty: the
UnoThrobberControl/Model work perfect. It is a nice alternative for
the progress bar control, and is the one used in the update dialog -
for OOo and also for extensions- , but also not documented in the
"brand-new" GUI chap. in the Dev's Guide :-(
Find sample code in issues:
http://www.openoffice.org/issues/show_bug.cgi?id=86415
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]
