brown@ftms.UUCP (Vidiot) (02/21/91)
Someone has suggested that to get rid of the title bar when olwm is used is to add `OpenWindows.MinimalDecor:<tab>prog1 prog2 ...' Well, I tried that, I tried adding -xrm to the shelltool startups, etc. and needless to say it appears as if this is just plain ignored. I wanted to use it with xv or xloadimage, ie, to bring up a picture without the title bar. No such luck. It will look like a picture frame without the title bar. Has anyone gotten this to work? And if so, how? Thanks in advance. -- harvard\ ucbvax!uwvax!astroatc!ftms!brown rutgers/ INTERNET: spool.cs.wisc.edu!astroatc!ftms!brown
smarks@trantor.Eng.Sun.COM (Stuart Marks) (02/22/91)
In article <23@ftms.UUCP>, brown@ftms.UUCP (Vidiot) writes: |> |> Someone has suggested that to get rid of the title bar when olwm is used is to |> add `OpenWindows.MinimalDecor:<tab>prog1 prog2 ...' |> |> Well, I tried that, I tried adding -xrm to the shelltool startups, etc. and |> needless to say it appears as if this is just plain ignored. The names you put in the MinimalDecor resource aren't always the same as the name of the program. The names for this resource must be the same as the strings the program gives in its WM_CLASS property. Also, the names are case-sensitive, so if the case doesn't match, the specification will be ignored. To find out what class xloadimage uses, I ran xloadimage and then I used xprop to look at the properties on xloadimage's window: WM_CLASS(STRING) = "", "Xloadimage" So you should put "Xloadimage" into the MinimalDecor resource. |> I wanted to use it with xv or xloadimage, ie, to bring up a picture without |> the title bar. No such luck. It will look like a picture frame without the |> title bar. I'm not sure what you mean by looking "like a picture frame without the title bar." If you set the MinimalDecor resource this way, olwm gets rid of the title bar, but there is still a thin border all the way around the edge of the window. This may or may not be what you want. s'marks -- Stuart W. Marks ARPA: smarks@eng.sun.com Windows & Graphics Software UUCP: sun!smarks Sun Microsystems, Inc.
dna@math.psu.edu (Douglas N. Arnold) (02/23/91)
In article <8388@exodus.Eng.Sun.COM>, smarks@Eng.Sun.COM (Stuart Marks) writes: >> In article <23@ftms.UUCP>, brown@ftms.UUCP (Vidiot) writes: >> |> >> |> Someone has suggested that to get rid of the title bar when olwm is used is to >> |> add `OpenWindows.MinimalDecor:<tab>prog1 prog2 ...' >> |> >> |> Well, I tried that, I tried adding -xrm to the shelltool startups, etc. and >> |> needless to say it appears as if this is just plain ignored. >> >> The names you put in the MinimalDecor resource aren't always the same as the >> name of the program. The names for this resource must be the same as the >> strings the program gives in its WM_CLASS property. Also, the names are >> case-sensitive, so if the case doesn't match, the specification will be >> ignored. >> >> To find out what class xloadimage uses, I ran xloadimage and then >> I used xprop to look at the properties on xloadimage's window: >> >> WM_CLASS(STRING) = "", "Xloadimage" >> >> So you should put "Xloadimage" into the MinimalDecor resource. What about applications like cmdtool or textedit. When I use xprop on these, it doesn't report any WM_CLASS. Is it possible to get rid of the title bar on these applications? -- Douglas N. Arnold dna@math.psu.edu Dept. of Mathematics, Penn State Univ. (814) 865-0246