On Thu, Feb 21, 2008 at 11:53:12PM +0800, for.register for.register wrote: > Thank you all , finally I found FvwmScript is a better choice for me. > And it is more easy to set and more flexible.
*Please* don't top-post on this mailing list! > On Thu, Feb 21, 2008 at 11:39 PM, Jesús Guerrero <[EMAIL PROTECTED]> wrote: > > > > On Thu, 21 Feb 2008 14:23:59 +0800 > > "for.register for.register" <[EMAIL PROTECTED]> wrote: > > > > > Hi, all > > > > > > Is it possible to make xclock transparent? > > > > > > Here is my config, it doesn't work. > > > Colorset 8 RootTransparent > > > Style XClock !Title, !Borders, Colorset 3, NeverFocus, \ > > > WindowListSkip, \ > > > CirculateSkip, StartsOnPage 0 0, Forecolor Colorset 3 > > > > > As someone already said, xclock can't be transparent because it just > > lacks that feature. I remember some kind of odd patch around, but that > > was a big time ago. I doub't you can find it anymore. You have a number of > > options: xdaliclock, dclock? (not sure about this one), oclock (probably > > the most similar one if you like analog clocks). And surely many more. > > > > You can also use FvwmScript. There are lots of clocks scripts around. > > > > And there're also the wmaker applets, but I don't know if any of these > > offer transparencies (they are convenient to be swallowd into fvwmbuttons, > > though. > > > > Fvwm colorsets can't do anything at all once you are on the client area > > of the window. > > > > -- > > Jesús Guerrero <[EMAIL PROTECTED]> > > > > Ciao Dominik ^_^ ^_^ -- Dominik Vogt
