FAQ.wm 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140
  1. /*************************************<+>*************************************
  2. *****************************************************************************
  3. **
  4. ** File: FAQ.wm
  5. **
  6. ** Project: Window/Workspace Manager
  7. **
  8. ** Description:
  9. ** -----------
  10. ** When we get a call from a "customer" we can refer to this
  11. ** list for an available answer, or, add any new information
  12. ** we gain from the call. Please try to group questions by topic.
  13. ** Add new topics as needed.
  14. **
  15. **
  16. *****************************************************************************
  17. **
  18. ** (c) Copyright 1990, 1991 Hewlett-Packard Company
  19. ** All Rights reserved
  20. **
  21. **
  22. *****************************************************************************
  23. *************************************<+>*************************************/
  24. /*
  25. * Focus Policy
  26. */
  27. Q. When the window/workspace manager keyboardFocusPolicy == pointer,
  28. how can I help the user dismiss one of my application's modal
  29. dialogs without forcing the user to move the mouse? Should I
  30. warp the pointer?
  31. A. If the user has chosen pointer focus policy, the user has declared that
  32. she wants to control the focus directly. We believe an application
  33. should not warp the pointer. [ In any case, when the user grows up,
  34. he will change to explicit keyboardFocusPolicy :-) ]
  35. /*
  36. * Backdrops
  37. */
  38. Q. I set a gif image into my root window, but I can't see it with DT.
  39. How come?
  40. A. DT normally covers the root windows with backdrops for each
  41. workspace. Your image is there, but the root window is covered, so
  42. you can't see it. To disable backdrops, add a resource like:
  43. Dtwm*<screen_name>*<workspace_name>*backdrop*image: none
  44. example:
  45. Dtwm*HighResHighColor*One*backdrop*image: none
  46. This disables backdrops for workspace One and lets the root window
  47. show through.
  48. /*
  49. * Killing Windows
  50. */
  51. Q. How do I stop the window manager from killing my client when the
  52. user double-clicks on the system menu box?
  53. A. There are two ways of approaching this.
  54. 1. Set the clientFunctions for your client to disable the "Close"
  55. item. This will work with mwm or dtwm. For example:
  56. Dtwm*Console*clientFunctions: -close
  57. disables "close" for the Console window.
  58. 2. Modify your client to follow the WM_DELETE_WINDOW protocol as
  59. described in the ICCCM. This will work with any window manager.
  60. If your client is Motif you can:
  61. a. Call XmAddWMProtocolCallback to add a WM_DELETE_WINDOW
  62. callback.
  63. b. Set XmNdeleteResponse to XmDO_NOTHING so that VendorShell
  64. won't destroy the window when the WM_DELETE_WINDOW comes
  65. in.
  66. This allows your client to post a "Are You Sure?" dialog when
  67. "Close" is activated. Your client decides when and if it should
  68. die in this case.
  69. /*
  70. * Geometry
  71. */
  72. /*
  73. * Making a window larger than the screen
  74. */
  75. Q. How can I map a window to be larger than the screen. For example
  76. I have a 14 inch monitor and I want my term windows to use a large font.
  77. The window manager does not let my term window map to a larger than
  78. screen size so I get less than 80 columns.
  79. A. There are a number of resources that affect this behavior
  80. 1) Set the "limitResize" resource to false.
  81. 2) The other thing is to specify an explicit maximum size for your
  82. term windows. Mwm/dtwm computes the maximum size to fit on the screen
  83. by default. You could do something like:
  84. Dtwm*xterm*maximumClientSize: 160x66
  85. so that 80x24 windows will come up regardless of whether they
  86. fit on the screen or not.
  87. 3) There may be other resource lurking out there (such as in
  88. /usr/lib/X11/app-defaults/Dtwm, xrdb, $HOME/Dtwm, etc.) that are more
  89. specific than the "*resource" specs you have given. If so, they'll
  90. win. Try being more specific. If that fixes it, then you'll probably
  91. want to find out where your resources are coming from (app-defaults,
  92. xrdb, $HOME/Dtwm, etc.).
  93. /*
  94. * Top/Bottom Shadows
  95. */
  96. /*
  97. * New Topic
  98. */