Yuri Dario wrote:
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.
Unix/X11 is like OS/2 with regard to parent/child clipping; on the X11
platforms all frames are created without a parent, however a hint to the
window manager is set that there is a connection (the window manager is
the application that decorates windows and allows user interaction) so
that the window manager can arrange e.g. dialogs always in front of
their "parent".
As for the coordinates, on Unix the coordinates are simply made relative
to their parent by adding the parent coordinates; SalFrame has a
maGeometry member that holds absolute screen positions (and needs to be
updated if the window is moved by the way).
interesting, so child style is not used to draw main gui parts in OOo.
The GUI parts like buttons, listboxes, etc. are not SalFrames (that is
actual system windows) at all. They are basically just clip regions and
that is all the system dependent Sal part ever sees of them. Only
windows that need to be separate system windows like application frames,
menu popups and dialogs lead to a SalFrame being created.
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]
