Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!uupsi!kepler1!fcaggian From: fcaggian@kepler.com (Frank Caggiano) Newsgroups: comp.windows.open-look Subject: Re: A suggestion for sticky windows in a .Xdefaults file for olvwm Summary: the title bar is to variable Keywords: olvwm sticky Message-ID: <585@kepler1.kepler.com> Date: 10 May 91 14:27:57 GMT References: <1991May3.000802.29165@wlbr.imsd.contel.com> <1077@redford.UUCP> <1991May9.174620.8589@wlbr.imsd.contel.com> Organization: Kepler Financial Mgmt., Setuket, NY Lines: 27 In article <1991May9.174620.8589@wlbr.imsd.contel.com>, mh@awds27.imsd.contel.com (Mike Hoegeman) writes: > > What do you think about using the window titles for determining what > should be sticky ?? You could have a resource that is a list of regular > expressions. If one of the expressions matches the window title the > window would be made sticky. The problem with this is that the title bar is, on the one hand too variable to uniquely identify a window you want sticky and on the other hand its not variable enough to differentiate between instances of an application. For example in my xterm and cmdtool windows I use the bar to display the machine I'm logged on the cwd and the directory stack, what regex would identify these windows uniquely. As another example I have three xclocks for displaying three timezones, the title bar has the timezone. In this case I would need three entries for the three windows instead of just one XClock entry. Finally my console window is the only xterm which I have sticky. The title bar is identical to other xterm windows, how would I make just this instance sticky? The WM_CLASS attribute is designed just for this type of idetification of windows. I don't belive the title bar would work nearlly as well. -- Frank Caggiano INTERNET: fcaggian@kepler.com Kepler Financial Management, Ltd. UUCP: ..!uunet!kepler1!fcaggian 100 North Country Rd. fax: (516) 751-8678 Sekauket, NY 11733 voice: (516) 689-6300