1 static char rcsid[] = "$XConsortium: FAQ.wm /main/3 1995/11/01 11:26:51 rswiston $";
3 /*************************************<+>*************************************
4 *****************************************************************************
8 ** Project: Window/Workspace Manager
12 ** When we get a call from a "customer" we can refer to this
13 ** list for an available answer, or, add any new information
14 ** we gain from the call. Please try to group questions by topic.
15 ** Add new topics as needed.
18 *****************************************************************************
20 ** (c) Copyright 1990, 1991 Hewlett-Packard Company
21 ** All Rights reserved
24 *****************************************************************************
25 *************************************<+>*************************************/
34 Q. When the window/workspace manager keyboardFocusPolicy == pointer,
35 how can I help the user dismiss one of my application's modal
36 dialogs without forcing the user to move the mouse? Should I
39 A. If the user has chosen pointer focus policy, the user has declared that
40 she wants to control the focus directly. We believe an application
41 should not warp the pointer. [ In any case, when the user grows up,
42 he will change to explicit keyboardFocusPolicy :-) ]
48 Q. I set a gif image into my root window, but I can't see it with DT.
51 A. DT normally covers the root windows with backdrops for each
52 workspace. Your image is there, but the root window is covered, so
53 you can't see it. To disable backdrops, add a resource like:
55 Dtwm*<screen_name>*<workspace_name>*backdrop*image: none
59 Dtwm*HighResHighColor*One*backdrop*image: none
61 This disables backdrops for workspace One and lets the root window
69 Q. How do I stop the window manager from killing my client when the
70 user double-clicks on the system menu box?
72 A. There are two ways of approaching this.
74 1. Set the clientFunctions for your client to disable the "Close"
75 item. This will work with mwm or dtwm. For example:
77 Dtwm*Console*clientFunctions: -close
79 disables "close" for the Console window.
82 2. Modify your client to follow the WM_DELETE_WINDOW protocol as
83 described in the ICCCM. This will work with any window manager.
84 If your client is Motif you can:
86 a. Call XmAddWMProtocolCallback to add a WM_DELETE_WINDOW
89 b. Set XmNdeleteResponse to XmDO_NOTHING so that VendorShell
90 won't destroy the window when the WM_DELETE_WINDOW comes
93 This allows your client to post a "Are You Sure?" dialog when
94 "Close" is activated. Your client decides when and if it should
104 * Making a window larger than the screen
108 Q. How can I map a window to be larger than the screen. For example
109 I have a 14 inch monitor and I want my term windows to use a large font.
110 The window manager does not let my term window map to a larger than
111 screen size so I get less than 80 columns.
113 A. There are a number of resources that affect this behavior
115 1) Set the "limitResize" resource to false.
117 2) The other thing is to specify an explicit maximum size for your
118 term windows. Mwm/dtwm computes the maximum size to fit on the screen
119 by default. You could do something like:
121 Dtwm*xterm*maximumClientSize: 160x66
123 so that 80x24 windows will come up regardless of whether they
124 fit on the screen or not.
126 3) There may be other resource lurking out there (such as in
127 /usr/lib/X11/app-defaults/Dtwm, xrdb, $HOME/Dtwm, etc.) that are more
128 specific than the "*resource" specs you have given. If so, they'll
129 win. Try being more specific. If that fixes it, then you'll probably
130 want to find out where your resources are coming from (app-defaults,
131 xrdb, $HOME/Dtwm, etc.).