From: Scott L. <sl...@cs...> - 2002-04-09 03:04:56
|
I still haven't been able to test the window manager hint stuff since I have found a way to display the options that I can understand. I can get stuff from xprop like this: 850> xprop WM_STATE(WM_STATE): window state: Normal icon window: 0x80015b _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0xbffffc84, 0x0, 0x8186fb0, 0x810f83c XdndAware(ATOM) = ARC _MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x18, 0x40, 0x10, 0x0, 0x0, 0x0 WM_CLASS(STRING) = "XMMS_Playlist", "xmms" WM_LOCALE_NAME(STRING) = "en_US" WM_CLIENT_MACHINE(STRING) = "strider" WM_ICON_NAME(STRING) = "XMMS Playlist" WM_NAME(STRING) = "XMMS Playlist" WM_CLIENT_LEADER(WINDOW): window id # 0x2a00001 WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. window id # of group leader: 0x2a00001 WM_NORMAL_HINTS(WM_SIZE_HINTS): program specified minimum size: 275 by 319 program specified maximum size: 275 by 319 WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS WM_TRANSIENT_FOR(WINDOW): window id # 0x2a0001a I thought I would look at the Motif hints first since they seem to be the most common, but I haven't been able to find anything that documents what _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0xbffffc84, 0x0, 0x8186fb0, 0x810f83c means. I've looked on Google a while but didn't find anything particularly useful. Any hints? - Scott |
From: Jason L. <low...@ea...> - 2002-04-09 15:37:56
|
The contents of the MOTIF_WM_HINTS atom is a C struct, which is defined in /usr/X11R6/include/Xm/MwmUtil.h as the struct "MotifWmHints". It's basically 5 ints that represent various bit-masked flags. By the way... I'm right in the middle of changing jobs, so my schedule is again in turmoil. I had been doing all my scwm stuff on my work laptop, which I have to return at the end of this week. I just bought a new laptop of my own to replace it and loaded Skipjack (Redhat 7.3 beta) from ISO's, so now I'm going to spend some time getting everything I need installed and configured (including scwm). And then in 2 weeks I'll be repeating this on my new work computer at my new job. *sigh* Later, Jason On Mon, 2002-04-08 at 21:04, Scott Lenser wrote: > > I still haven't been able to test the window manager hint stuff > since I have found a way to display the options that I can > understand. I can get stuff from xprop like this: > > 850> xprop > WM_STATE(WM_STATE): > window state: Normal > icon window: 0x80015b > _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0xbffffc84, 0x0, 0x8186fb0, 0x810f83c > XdndAware(ATOM) = ARC > _MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x18, 0x40, 0x10, 0x0, 0x0, 0x0 > WM_CLASS(STRING) = "XMMS_Playlist", "xmms" > WM_LOCALE_NAME(STRING) = "en_US" > WM_CLIENT_MACHINE(STRING) = "strider" > WM_ICON_NAME(STRING) = "XMMS Playlist" > WM_NAME(STRING) = "XMMS Playlist" > WM_CLIENT_LEADER(WINDOW): window id # 0x2a00001 > WM_HINTS(WM_HINTS): > Client accepts input or input focus: True > Initial state is Normal State. > window id # of group leader: 0x2a00001 > WM_NORMAL_HINTS(WM_SIZE_HINTS): > program specified minimum size: 275 by 319 > program specified maximum size: 275 by 319 > WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS > WM_TRANSIENT_FOR(WINDOW): window id # 0x2a0001a > > > I thought I would look at the Motif hints first since they seem to > be the most common, but I haven't been able to find anything that > documents what > > _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0xbffffc84, 0x0, 0x8186fb0, 0x810f83c > > means. I've looked on Google a while but didn't find anything particularly > useful. Any hints? > > - Scott > > |
From: Scott L. <sl...@cs...> - 2002-04-04 17:09:21
|
Ah, cool. I didn't know about xprop. Also, I just looked at it looks like I might be able to use 'X-get-property' plus some extra code to find all the properties. Thanks. - Scott > The only way I know to see what hints an app has set is to use xprop to > look at the window's properties. For example the mwm hints go into an > atom called MOTIF_WM_HINTS. You might be able to tell from the code > exactly what atoms correspond to each of those hints. I'll take a look > at some of the apps on my system to see if I come across any of the > one's you're looking for. > > Jason > > On Thu, 2002-04-04 at 00:53, Scott Lenser wrote: > > > > I've mostly finished testing style.scm. Ugh, this file is > > annoying :-(. I wasn't able to test the following functions > > because I need to find apps that set the hints and I don't know > > how to check reasonably easily whether an app uses these hints > > and I don't know which apps set this hints. This is where the > > help comes in. I need to find apps that set these hints. If you > > know of such apps I can just use them. If you know how to > > check what hints an app has set I can look through a lot of apps > > that seem likely to be setting hints until I find ones to use > > to test these hints. > > > > The untested hint stuff is: > > > > #:hint-override, #:mwm-decor-hint, #:mwm-func-hint, > > #:PPosition-hint, #:OL-decor-hint, #:lenience > > |
From: Scott L. <sl...@cs...> - 2002-04-09 16:55:10
|
> The contents of the MOTIF_WM_HINTS atom is a C struct, which is defined > in /usr/X11R6/include/Xm/MwmUtil.h as the struct "MotifWmHints". It's > basically 5 ints that represent various bit-masked flags. > > Later, > > Jason > Ah, great! Now I can test the motif stuff at least. This documentation makes sense to me. - Scott |