From: Lucas H. <luc...@di...> - 2005-02-07 10:22:32
|
On Mon, 07 Feb 2005 11:15:51 +0000 Dominic <lsd...@nt...> wrote: > Alex Kloss wrote: > > On Sun, 06 Feb 2005 17:28:49 +0000 > > > Hi, Dom! > > > > Pseudo-transparency (or even real transparency) should be not too > > difficult, but is not what I should call useful functionality. It's > > the kind of eyecandy that tends to get in the way, makes it harder > > to read the text and/or recognize the icons. One of the rare real > > useful uses of transparency could be within a window manager to make > > unused windows transparent, so they don't block other windows from > > sight. > > But with some light shading I would be able to see my beautiful > background underneath, plus I'm sure there's a handful of people like > me who like eye-candy (without resorting to bloat). And it could be > optional at compile time anyway. If i had any idea where to start I'd > > add it in myself, can't be too difficult... :S > If you want rox to have optional transparency, you would have a better chance making some noise on the gtk mailing lists. To do this natively in rox would require a new widget class. If you use devilspie and are using the Xcomposite extension you can do this already. The latest version has a set opacity option. -- Lucas Hazel <lu...@di...> Student, BSDfreak University of New England (http://cs.une.edu.au) Armidale, Australia [http://www.digitillogic.net] ================================================= "Clothes make the man. Naked men are rarely taken seriously, or given employment." (Mark Twain) ================================================= |