Path: utzoo!utgpu!watmath!att!dptg!rutgers!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!agate!root From: csvsj@garnet.berkeley.edu (Steve Jacobson) Newsgroups: comp.windows.x Subject: Keyboard Focus and OverrideShells Keywords: twm, ICCCM, dxwm Message-ID: <1989Aug10.001831.13428@agate.berkeley.edu> Date: 10 Aug 89 00:18:31 GMT Reply-To: csvsj@garnet.berkeley.edu (Steve Jacobson) Organization: University of California, Berkeley Lines: 28 We developed our complex X client on machines running twm. When we tried running it on a Decstation 3100 running dxsession and dxwm, we had problems with color map use and keyboard focus. We usually run twm on the Decstation now, but we've tried to become ICCCM compliant - we assumed some of our problems might be ICCCM related. We don't install our custom colormap anymore and we use XSetWindowColormap() to let the window manager know about desired maps. This method works with twm and dxwm. Noting the recent comp.windows.x keyboard focus discussion, we tried setting XtNinput true for the top level shell where we want keyboard focus. This worked - dxwm now lets the client get keyboard focus. However, we use a override shell popup window that includes a widget that accepts typed input. Under dxsession/dxwm, this widget doesn't receive keyboard focus, even with XtNinput set to true. Since an override class shell bypasses the window manager, I guess it makes sense that an option to set a window manager hint wouldn't do anything. Does this mean that an override class shell can't contain a widget that expects keyboard input? Or is dxsession/dxwm behaving incorrectly?