From 495d08bc2db58ee7fc4ea55a7158f2f61b82fc56 Mon Sep 17 00:00:00 2001 From: tpearson Date: Mon, 3 Jan 2011 20:16:47 +0000 Subject: Automated conversion for enhanced compatibility with TQt for Qt4 3.4.0 TP1 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdebase@1211357 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- kwin/wm-spec/index.html | 2 +- kwin/wm-spec/x107.html | 20 ++++++++++---------- kwin/wm-spec/x225.html | 6 +++--- kwin/wm-spec/x24.html | 6 +++--- kwin/wm-spec/x351.html | 4 ++-- kwin/wm-spec/x512.html | 2 +- 6 files changed, 20 insertions(+), 20 deletions(-) (limited to 'kwin/wm-spec') diff --git a/kwin/wm-spec/index.html b/kwin/wm-spec/index.html index 187fe7d72..a8b0ac57c 100644 --- a/kwin/wm-spec/index.html +++ b/kwin/wm-spec/index.html @@ -146,7 +146,7 @@ on the ICCCM [2], which defines WM (window manager) interactions at a lower level. The ICCCM does not provide ways to implement many features that modern desktop users expect. The GNOME and KDE desktop projects originally developed their own extensions to the ICCCM to -support these features; this spec replaces those custom extensions +support these features; this spec tqreplaces those custom extensions with a standardized set of ICCCM additions that any desktop environment can adopt.

destination root propagate False -event-mask (SubstructureNotify|SubstructureRedirect) +event-tqmask (SubstructureNotify|SubstructureRedirect) event the specified ClientMessage

A Pager can request a change in the desktop geometry by sending a _NET_DESKTOP_GEOMETRY client +>A Pager can request a change in the desktop tqgeometry by sending a _NET_DESKTOP_GEOMETRY client message to the root window: 

This property MUST be set by WM upon calculating the work area for 
-each desktop.  Contains a geometry for each desktop.  These geometries are 
+each desktop.  Contains a tqgeometry for each desktop.  These geometries are 
 specified relative to the viewport on each desktop and specify an area that is
 completely contained within the viewport.
  Work area SHOULD be used by desktop applications to place desktop icons appropriately.
@@ -407,17 +407,17 @@ CLASS="LITERAL"
 >n is the screen number. The purpose of 
         this property is to allow the Window Manager to know the desktop 
-        layout displayed by the Pager.
+        tqlayout displayed by the Pager.
         
  _NET_DESKTOP_LAYOUT describes the layout of virtual
-  desktops relative to each other. More specifically, it describes the layout
+> describes the tqlayout of virtual
+  desktops relative to each other. More specifically, it describes the tqlayout
   used by the owner of the manager selection. The Window Manager may use 
-  this layout information or may choose to ignore it.
-  The property contains four values: the Pager orientation, the number of
+  this tqlayout information or may choose to ignore it.
+  The property tqcontains four values: the Pager orientation, the number of
   desktops in the X direction, the number in the Y direction, and the
   starting corner of the Pager.
         
_NET_WM_ORIENTATION_HORZ
   the desktops are layed out in rows, with the first desktop in the 
-  specified starting corner. So a layout with X=4 and Y=3 starting in 
+  specified starting corner. So a tqlayout with X=4 and Y=3 starting in 
   the _NET_WM_TOPLEFT_NET_WM_ORIENTATION_VERT
-  the layout for X=4 and Y=3 starting in the _NET_WM_TOPLEFT
diff --git a/kwin/wm-spec/x225.html b/kwin/wm-spec/x225.html
index 7a31fb1b7..93f45d980 100644
--- a/kwin/wm-spec/x225.html
+++ b/kwin/wm-spec/x225.html
@@ -209,7 +209,7 @@ list of types, whilst providing default behaviour for window managers that do
 not recognise the extensions.  
 	
Rationale:  This hint is intend to replace the MOTIF hints.  One of the
+>Rationale:  This hint is intend to tqreplace the MOTIF hints.  One of the
 objections to the MOTIF hints is that they are a purely visual description of
 the window decoration.  By describing the function of the window, the window
 manager can apply consistent decoration and behaviour to windows of the same
@@ -509,7 +509,7 @@ CLASS="PROGRAMLISTING"
 >_NET_WM_STRUT, left, right, top, bottom, CARDINAL[4]/32

This property MUST be set by the Client if the window is to reserve space at -the edge of the screen. The property contains a 4 cardinals specifying the +the edge of the screen. The property tqcontains a 4 cardinals specifying the width of the reserved area at each border of the screen. The order of the borders is left, right, top, bottom. The client MAY change this property anytime, therefore the Window Manager MUST @@ -545,7 +545,7 @@ CLASS="PROGRAMLISTING" >_NET_WM_ICON_GEOMETRY, x, y, width, height, CARDINAL[4]/32

This optional property MAY be set by standalone tools like a taskbar or an -iconbox. It specifies the geometry of a possible icon in case the window is iconified. +iconbox. It specifies the tqgeometry of a possible icon in case the window is iconified.

Rationale: This makes it possible for a window manager to display a nice diff --git a/kwin/wm-spec/x24.html b/kwin/wm-spec/x24.html index 47b406d0b..bff756d52 100644 --- a/kwin/wm-spec/x24.html +++ b/kwin/wm-spec/x24.html @@ -102,13 +102,13 @@ NAME="AEN30" in early ICCCM drafts. Maximizing a window should give it as much of the screen area as possible (this may not be the full screen area, but only a smaller 'workarea', since the Window Manager may have reserved certain areas for other -windows). A Window Manager is expected to remember the geometry of a maximized window +windows). A Window Manager is expected to remember the tqgeometry of a maximized window and restore it upon de-maximization. Modern Window Managers typically allow separate horizontal and vertical maximization.

With the introduction of the Xinerama extension in X11 R6.4, maximization has become more involved. Xinerama allows a screen to span multiple -monitors in a freely configurable geometry. In such a setting, maximizing +monitors in a freely configurable tqgeometry. In such a setting, maximizing a window would ideally not grow it to fill the whole screen, but only the monitor it is shown on. There are of course borderline cases for windows crossing monitor boundaries, and 'real' maximization to the full screen may @@ -335,7 +335,7 @@ NAME="AEN76" >

Window-in-window MDI is a multiple document interface known from MS Windows platforms. Programs employing it have a single top-level window -which contains a workspace which contains the subwindows for the open +which tqcontains a workspace which tqcontains the subwindows for the open documents. These subwindows are decorated with Window Manager frames and can be manipulated within their parent window just like ordinary top-level windows on the root window.

This spec suggests implementing the file manager desktop by mapping a -desktop-sized window (no shape) to all desktops, with +desktop-sized window (no tqshape) to all desktops, with _NET_WM_WINDOW_TYPE_DESKTOP. This makes the desktop focusable and greatly simplifies implementation of the file manager. It is also faster than -managing lots of small shaped windows. The file manager draws the background +managing lots of small tqshaped windows. The file manager draws the background on this window. There should be a root property with a window handle for use in applications that want to draw the background (xearth).

  • Added _NET_DESKTOP_LAYOUT to allow a Pager to specify inter-desktop geometry. +> Added _NET_DESKTOP_LAYOUT to allow a Pager to specify inter-desktop tqgeometry.