Hi,
>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.
now I see things better: I thought that win32 windows were always
clipped by parent handle specified in CreateWindowEx, but this is true
only for WS_CHILD style; POPUP and OVERLAPPED styles lets windows to be
drawn outside the parent.
Under OS/2, when a parent window is specified, this always is clipping
the childrens, so this explain why older os2 code was using the desktop
as handle for parent.
How do unix people fix the coordinates? maybe I can take the same
approach. Now I'm using the owner window handle to compute relative
position, but this is not always working.
>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.
interesting, so child style is not used to draw main gui parts in OOo.
Thanks,
Bye,
Yuri Dario
/*
* member of TeamOS/2 - Italy
* http://www.os2power.com/yuri
* http://www.teamos2.it
*/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
