Yuri Dario wrote:
I worked a bit more on this, and following the win32 code, I used the
same criteria to create new windows (old OS2 code was creating windows
using desktop as parent, so coordinates are different).
So using the OOo supplied parent makes coordinate system working as
designed, but I faced another problem: since a child cannot paint
outside his parent, I'm unable to show submenus. E.g. a first level
menu is drawed correctly because its parent is the main window, but a
second level menu has the first-level as parent, so it draws only
partially.
Most windows of SalFrame are not actually created with the style
WS_CHILD (which makes them real child windows constrained inside the
parent). If OS/2 does not also have this peculiar distinction, then you
might be better of with the Unix approach; in there only very rarely a
window is created as an actual child of a system window.
WS_CHILD (in Windows terminology) is only needed for the SalObject class
(which provides a container for plugins and the like) and for frames
with the SAL_FRAME_STYLE_CHILD (caution: this is not a system style but
the style abstraction of SalFrame itself). The latter are used for
embeding VCL windows into other system windows, e.g. when OOo runs as a
plugin in a browser or is embedded into a java application.
Kind regards, pl
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
