Re: FVWM: can xcompmgr work in fvwm config?
The Module FvwmTransFocus is good enough, but there is still a little thing: I use iconfy with thumbnail, and it is tranparent, but after my mouse leave the thumbnail and move into another window, unlike other nomal windows, thouse thumbnails wont go back to tranparent. here is my corresponding config: KillModule FvwmTransFocus Module FvwmTransFocus 0.9 0.5 0.7 Colorset 3 fg #77, bg #ff, fgsh #bb, RootTransparent, \ Tint #283e5e 70, IconAlpha 20 Colorset 4 fg #00, bg #ff, fgsh #bb, RootTransparent, \ Tint #101f36 70, IconAlpha 100 # This make Thumbnail transparent when not focus Style * Colorset 3, HilightColorset 4 SetEnv fvwm_icon_size 100 DestroyFunc Thumbnail AddToFunc Thumbnail + I Raise + I SetEnv Icon-$[w.id] $[w.iconfile] + I ThisWindow (!Shaded Iconifiable !Iconic) \ PipeRead xwd -silent -id $[w.id] | convert -scale \ $[fvwm_icon_size] -frame 1x1 -mattecolor black -quality 0 \ xwd:- png:$[FVWM_USERDIR]/icon.tmp.$[w.id].png \ echo WindowStyle IconOverride,\ Icon $[FVWM_USERDIR]/icon.tmp.$[w.id].png || echo Nop + I TestRc (Match) Test (f $[HOME]/icons/$[w.miniiconfile]) \ PipeRead composite -geometry +2+4 \ $[HOME]/icons/$[w.miniiconfile] \ $[FVWM_USERDIR]/icon.tmp.$[w.id].png \ $[FVWM_USERDIR]/icon.tmp.$[w.id].png \ echo Nop || echo Beep + I Iconify DestroyFunc DeThumbnail AddToFunc DeThumbnail + I PipeRead echo WindowStyle Icon \\$\\[Icon-$[w.id]\\] + I UnsetEnv Icon-$[w.id] + I Exec exec rm -f $[FVWM_USERDIR]/icon.tmp.$[w.id].png On Feb 8, 2008 4:08 PM, for.register for.register [EMAIL PROTECTED] wrote: Perfect! Thanks for your programs. On Feb 8, 2008 3:14 AM, Michal Nazarewicz [EMAIL PROTECTED] wrote: for.register for.register [EMAIL PROTECTED] writes: Here is my config Here is debug info.Module FvwmDebug --log '|xconsole -file /dev/stdin -geometry 600x400 -notify' KillModule FvwmTransFocus Module FvwmTransFocus 0.9 0.5 0.1 [...] OK, it turned out that I was using older version of this module (I could swore I installed the new one O_o). For the time being you can download it from CVS[1] (it has the same functionality) and I'll work on a fix. [1] http://tinyapps.cvs.sourceforge.net/*checkout*/tinyapps/tinyapps/FvwmTransFocus.c?revision=1.7 -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
for.register for.register [EMAIL PROTECTED] writes: I use iconfy with thumbnail, and it is tranparent, but after my mouse leave the thumbnail and move into another window, unlike other nomal windows, thouse thumbnails wont go back to tranparent. I think that the problem is that icons are drawn directly on the root window (or something) and thus they don't take or loose focus. I'll try to investigate it a bit more but can't say I'll come up with anything. -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
Perfect! Thanks for your programs. On Feb 8, 2008 3:14 AM, Michal Nazarewicz [EMAIL PROTECTED] wrote: for.register for.register [EMAIL PROTECTED] writes: Here is my config Here is debug info.Module FvwmDebug --log '|xconsole -file /dev/stdin -geometry 600x400 -notify' KillModule FvwmTransFocus Module FvwmTransFocus 0.9 0.5 0.1 [...] OK, it turned out that I was using older version of this module (I could swore I installed the new one O_o). For the time being you can download it from CVS[1] (it has the same functionality) and I'll work on a fix. [1] http://tinyapps.cvs.sourceforge.net/*checkout*/tinyapps/tinyapps/FvwmTransFocus.c?revision=1.7 -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
for.register for.register [EMAIL PROTECTED] writes: After I start xcompmgr, FvwmTransButtons works. But a little problem, About the three parameters, new works well, however, active and inactive have the same transparency, after toggle between active and inactive once. Both of them use the active transparency. active - opacity of active windows (default: 0.8) inactive - opacity of inactive windows (default: 0.6) new - opacity of newly created windows (default: inactive Bizarre. Could you compile FvwmTransSet with debug enabled (-DDEBUG=1 as a compiler option) and then provide output that is generated to FVWM's standard error stream (probably first terminal where X was started from). On Feb 7, 2008 3:11 PM, for.register wrote: Thanks, I have tried, but seems FvwmTransFocus doesn't work for me, probably my compiling parameters is not correct. I read the FvwmTransFocus.c, but I did not find the /usr/X11R6/include, and /usr/X11R6/lib, seems XFree86 and Xorg difference. I guess probably /usr/X11R6/include means /usr/include/xorg //usr/X11R6/lib means /usr/lib/xorg Makefile has some lame code for detecting X library and include files directory. -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
for.register for.register [EMAIL PROTECTED] writes: Here is my config Here is debug info.Module FvwmDebug --log '|xconsole -file /dev/stdin -geometry 600x400 -notify' KillModule FvwmTransFocus Module FvwmTransFocus 0.9 0.5 0.1 [...] OK, it turned out that I was using older version of this module (I could swore I installed the new one O_o). For the time being you can download it from CVS[1] (it has the same functionality) and I'll work on a fix. [1] http://tinyapps.cvs.sourceforge.net/*checkout*/tinyapps/tinyapps/FvwmTransFocus.c?revision=1.7 -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
Cameron Simpson [EMAIL PROTECTED] writes: On 06Feb2008 00:37, Michal Nazarewicz [EMAIL PROTECTED] wrote: | for.register for.register [EMAIL PROTECTED] writes: | I used to xcompmgr in fluxbox, since I can set different alpha value | in ~/.fluxbox/init for different transparency. For focus window, | transparency can be set to 1%, mean while unfocus windown can set to | 90%. My question is can I do the same thing in fvwm under xcompmgr? | | I've written it in another thread, so sorry for repeating: I've written | a module which does this -- it can be obtained from tinyapps.sf.net. | I'm using it ever since I've started using FVWM. I expect you can also do it using FvwmEvent, watching the focus change events. Probably yes, if you don't mind tons of spawned processes. I've originally written FvwmTransFocus because I felt like running two now processes when focus is changed is too much. -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
Here is my config Here is debug info.Module FvwmDebug --log '|xconsole -file /dev/stdin -geometry 600x400 -notify' KillModule FvwmTransFocus Module FvwmTransFocus 0.9 0.5 0.1 Here is the debug info: FvwmTransFocus: M_FOCUS_CHANGE recieved[FvwmPager][FlocaleGetFontSet]: (-*-fixed-medium-r-semicondensed-*-13-*-*-*-*-*-*-*,-*-fixed-medium-r-normal-*-14-*-*-*-*-*-*-*,-*-*-medium-r-normal-*-16-*-*-*-*-*-*-*) Missing font charsets: GB2312.1980-0, GBK-0 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: M_ADD_WINDOW recievedFvwmTransFocus: ClassHint: 'FvwmPager'; 'FvwmPager' FvwmTransFocus: Changing 0x006001d0's opacity to 0.10 FvwmTransFocus: M_FOCUS_CHANGE recievedNo running windows found FvwmTransFocus: M_ADD_WINDOW recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.10 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: M_ADD_WINDOW recievedFvwmTransFocus: Changing 0x0060029f's opacity to 0.10 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x0060029f's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x0060029f's opacity to 0.90 Synaptics DeviceOff called Synaptics DeviceOn called FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x0060029f's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.90 FvwmTransFocus: M_FOCUS_CHANGE recievedFvwmTransFocus: Changing 0x006001ee's opacity to 0.90 On Feb 7, 2008 7:03 PM, Michal Nazarewicz [EMAIL PROTECTED] wrote: for.register for.register [EMAIL PROTECTED] writes: After I start xcompmgr, FvwmTransButtons works. But a little problem, About the three parameters, new works well, however, active and inactive have the same transparency, after toggle between active and inactive once. Both of them use the active transparency. active - opacity of active windows (default: 0.8) inactive - opacity of inactive windows (default: 0.6) new - opacity of newly created windows (default: inactive Bizarre. Could you compile FvwmTransSet with debug enabled (-DDEBUG=1 as a compiler option) and then provide output that is generated to FVWM's standard error stream (probably first terminal where X was started from). On Feb 7, 2008 3:11 PM, for.register wrote: Thanks, I have tried, but seems FvwmTransFocus doesn't work for me, probably my compiling parameters is not correct. I read the FvwmTransFocus.c, but I did not find the /usr/X11R6/include, and /usr/X11R6/lib, seems XFree86 and Xorg difference. I guess probably /usr/X11R6/include means /usr/include/xorg //usr/X11R6/lib means /usr/lib/xorg Makefile has some lame code for detecting X library and include files directory. -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
I think xcompmgr plus transset themselves can not changes windows' opacity depending on focusfocus change, so I tried FvwmTransFocus from tinyapps.sf.net. But for me it doesn't work, here is my steps. ( I use gentoo linux) (1) complie FvwmTransFocus cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer -I/usr/include/X11 -L/usr/lib/X11 -o FvwmTransFocus FvwmTransFocus.c (2) cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ (3) In .fvwm/config add the following line: DestroyFunc StartFunction AddToFunc StartFunction + I Module FvwmPager 0 0 + I Module FvwmButtons + I Test (Init) Module FvwmTransFocus On Feb 6, 2008 1:15 PM, Cameron Simpson [EMAIL PROTECTED] wrote: On 06Feb2008 00:37, Michal Nazarewicz [EMAIL PROTECTED] wrote: | for.register for.register [EMAIL PROTECTED] writes: | I used to xcompmgr in fluxbox, since I can set different alpha value | in ~/.fluxbox/init for different transparency. For focus window, | transparency can be set to 1%, mean while unfocus windown can set to | 90%. My question is can I do the same thing in fvwm under xcompmgr? | | I've written it in another thread, so sorry for repeating: I've written | a module which does this -- it can be obtained from tinyapps.sf.net. | I'm using it ever since I've started using FVWM. I expect you can also do it using FvwmEvent, watching the focus change events. -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ It's a vague science. - Rory Tate, circle researcher.
Re: FVWM: can xcompmgr work in fvwm config?
On Wed, 6 Feb 2008 16:47:02 +0800 for.register for.register [EMAIL PROTECTED] wrote: But for me it doesn't work, here is my steps. ( I use gentoo linux) (1) complie FvwmTransFocus cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer -I/usr/include/X11 -L/usr/lib/X11 -o FvwmTransFocus FvwmTransFocus.c (2) cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ (3) In .fvwm/config add the following line: DestroyFunc StartFunction AddToFunc StartFunction + I Module FvwmPager 0 0 + I Module FvwmButtons + I Test (Init) Module FvwmTransFocus The test shouldn't be there. All the fvwm modules are killed on restart, so, with Test (init) the module will *only* be loaded on start, and not on restarts. Just like any other fvwm module. -- Jesús Guerrero [EMAIL PROTECTED]
Re: FVWM: can xcompmgr work in fvwm config?
On 06Feb2008 07:24, Jesús Guerrero [EMAIL PROTECTED] wrote: | I expect you can also do it using FvwmEvent, watching the focus change | events. | | Probably, I never player with this things. But don't get too happy about xcompmgr. Well, I'm fairly happy. I run it all the time at work. | It is old, it is buggy (depending on the options you use) It's pretty stable for me like this: xcompmgr -cfF -r0 -D5 -I0.01 -O0.02 with lots of windows and for days on end, maybe weeks. | and it doesn't use any | hardware acceleration. It will eat your cpu if you need to move a bin window | from one page to another. It was just a tool designed to showcase xcomposite, | xdamage and all the new technologies that arised in xorg. But it is just that: | a toy. I had presumed that xcomposite and friends took care of the hw acceleration if the video driver supported it. Certainly on my laptop it is an utter dog, but on the machine at work it's pretty snappy with the swanky NVidia card and nvidia driver. So much faster that the card _must_ be doing a lot of work. But I freely confess to not understanding the ins and outs of Xorg's graphics layers, and would be happy to hear a cogent explaination. Cheers, -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ The TV business is a cruel and shallow money trench, a long plastic hallway where thieves and pimps run free and good men die like dogs. - Hunter S Thompson
Re: FVWM: can xcompmgr work in fvwm config?
On Wed, 6 Feb 2008 20:31:34 +1100 Cameron Simpson [EMAIL PROTECTED] wrote: | It is old, it is buggy (depending on the options you use) It's pretty stable for me like this: xcompmgr -cfF -r0 -D5 -I0.01 -O0.02 with lots of windows and for days on end, maybe weeks. It is not stable for me even if I just use -n, but as people say: your mileage may vary. It gives problems specially with programs that use Xshape, like amarok, xmms, xosd and the like. That's the beauty of OSS: everyone can use whatever suits him/her better. :) | and it doesn't use any | hardware acceleration. It will eat your cpu if you need to move a bin window | from one page to another. It was just a tool designed to showcase xcomposite, | xdamage and all the new technologies that arised in xorg. But it is just that: | a toy. I had presumed that xcomposite and friends took care of the hw acceleration if the video driver supported it. Certainly on my laptop it is an utter dog, but on the machine at work it's pretty snappy with the swanky NVidia card and nvidia driver. So much faster that the card _must_ be doing a lot of work. Xcompmgr does not take advantage of any advanced feature, like the GLX_EXT_texture_from_pixmap extension that I talked about on the other thread. In fact, that extension is way too recent, and xcompmgr has not been updated since 2005, I think. I just talk by experience, I don't know anything about xcompmgr, but my card and my drivers DO support that extension, and cpu usage in beryl is next to zero, while with Xcompmgr it is awful. I would like to hear a more technical explanation as well, I don't know anything about the internals of this all. Cheers :) -- Jesús Guerrero [EMAIL PROTECTED]
Re: FVWM: can xcompmgr work in fvwm config?
On Feb 6, 2008 9:56 AM, Jesús Guerrero [EMAIL PROTECTED] wrote: On Wed, 6 Feb 2008 20:31:34 +1100 Cameron Simpson [EMAIL PROTECTED] wrote: (...) | and it doesn't use any | hardware acceleration. It will eat your cpu if you need to move a bin window | from one page to another. It was just a tool designed to showcase xcomposite, | xdamage and all the new technologies that arised in xorg. But it is just that: | a toy. I had presumed that xcomposite and friends took care of the hw acceleration if the video driver supported it. Certainly on my laptop it is an utter dog, but on the machine at work it's pretty snappy with the swanky NVidia card and nvidia driver. So much faster that the card _must_ be doing a lot of work. Xcompmgr does not take advantage of any advanced feature, like the GLX_EXT_texture_from_pixmap extension that I talked about on the other thread. In fact, that extension is way too recent, and xcompmgr has not been updated since 2005, I think. I just talk by experience, I don't know anything about xcompmgr, but my card and my drivers DO support that extension, and cpu usage in beryl is next to zero, while with Xcompmgr it is awful. I would like to hear a more technical explanation as well, I don't know anything about the internals of this all. Xcompmgr doesn't use that extension because it is not opengl accelerated. On the other hand, I believe compiz is (or was) opengl accelerated, which required some nested X hacks for it to work. But being opengl accelerated has little to do with being hardware accelerated, as opengl is only a high level API to the hw 3d engine. The XRender extension is hw accelerated, and even fvwm takes advantage from it when acceleration is enabled. I believe (haven't looked at the code) that xcompmgr is using the XRender acceleration. I believe the xorg.conf option for nvidia closed source driver is IIRC this: Option RenderAccel true For the open source hw accelerated driver (nouveau) that I'm currently using, use this: Option AccelMethod EXA Hope this helps. Cheers, Renato
Re: FVWM: can xcompmgr work in fvwm config?
for.register for.register [EMAIL PROTECTED] writes: I think xcompmgr plus transset themselves can not changes windows' opacity depending on focusfocus change, so I tried FvwmTransFocus from tinyapps.sf.net. But for me it doesn't work, here is my steps. ( I use gentoo linux) (1) complie FvwmTransFocus cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer -I/usr/include/X11 -L/usr/lib/X11 -o FvwmTransFocus FvwmTransFocus.c (2) cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ (3) In .fvwm/config add the following line: DestroyFunc StartFunction AddToFunc StartFunction + I Module FvwmPager 0 0 + I Module FvwmButtons + I Test (Init) Module FvwmTransFocus I have following lines in my FVWM config and everything works: KillModule FvwmTransFocus Module FvwmTransFocus 0.8 0.6 0.6 Did you run xcompmgr? -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
Thanks, I have tried, but seems FvwmTransFocus doesn't work for me, probably my compiling parameters is not correct. I read the FvwmTransFocus.c, but I did not find the /usr/X11R6/include, and /usr/X11R6/lib, seems XFree86 and Xorg difference. I guess probably /usr/X11R6/include means /usr/include/xorg //usr/X11R6/lib means /usr/lib/xorg so I complied with para without errors. #cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer \ -I/usr/include/X11 -L/usr/lib/X11 -lX11 -o FvwmTransFocus \ FvwmTransFocus.c then cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ Any advice? Thanks in advance. On Feb 6, 2008 11:36 PM, Michal Nazarewicz [EMAIL PROTECTED] wrote: for.register for.register [EMAIL PROTECTED] writes: I think xcompmgr plus transset themselves can not changes windows' opacity depending on focusfocus change, so I tried FvwmTransFocus from tinyapps.sf.net. But for me it doesn't work, here is my steps. ( I use gentoo linux) (1) complie FvwmTransFocus cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer -I/usr/include/X11 -L/usr/lib/X11 -o FvwmTransFocus FvwmTransFocus.c (2) cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ (3) In .fvwm/config add the following line: DestroyFunc StartFunction AddToFunc StartFunction + I Module FvwmPager 0 0 + I Module FvwmButtons + I Test (Init) Module FvwmTransFocus I have following lines in my FVWM config and everything works: KillModule FvwmTransFocus Module FvwmTransFocus 0.8 0.6 0.6 Did you run xcompmgr? -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
After I start xcompmgr, FvwmTransButtons works. But a little problem, About the three parameters, new works well, however, active and inactive have the same transparency, after toggle between active and inactive once. Both of them use the active transparency. active - opacity of active windows (default: 0.8) inactive - opacity of inactive windows (default: 0.6) new - opacity of newly created windows (default: inactive On Feb 7, 2008 3:11 PM, for.register for.register [EMAIL PROTECTED] wrote: Thanks, I have tried, but seems FvwmTransFocus doesn't work for me, probably my compiling parameters is not correct. I read the FvwmTransFocus.c, but I did not find the /usr/X11R6/include, and /usr/X11R6/lib, seems XFree86 and Xorg difference. I guess probably /usr/X11R6/include means /usr/include/xorg //usr/X11R6/lib means /usr/lib/xorg so I complied with para without errors. #cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer \ -I/usr/include/X11 -L/usr/lib/X11 -lX11 -o FvwmTransFocus \ FvwmTransFocus.c then cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ Any advice? Thanks in advance. On Feb 6, 2008 11:36 PM, Michal Nazarewicz [EMAIL PROTECTED] wrote: for.register for.register [EMAIL PROTECTED] writes: I think xcompmgr plus transset themselves can not changes windows' opacity depending on focusfocus change, so I tried FvwmTransFocus from tinyapps.sf.net. But for me it doesn't work, here is my steps. ( I use gentoo linux) (1) complie FvwmTransFocus cc -march=prescott -O3 -pipe -msse3 -fomit-frame-pointer -I/usr/include/X11 -L/usr/lib/X11 -o FvwmTransFocus FvwmTransFocus.c (2) cp FvwmTransFocus /usr/lib/fvwm/2.5.21/ (3) In .fvwm/config add the following line: DestroyFunc StartFunction AddToFunc StartFunction + I Module FvwmPager 0 0 + I Module FvwmButtons + I Test (Init) Module FvwmTransFocus I have following lines in my FVWM config and everything works: KillModule FvwmTransFocus Module FvwmTransFocus 0.8 0.6 0.6 Did you run xcompmgr? -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Fw: Re: FVWM: can xcompmgr work in fvwm config?
Begin forwarded message: Date: Tue, 5 Feb 2008 17:35:17 +0100 From: Jesús Guerrero [EMAIL PROTECTED] To: for.register for.register [EMAIL PROTECTED] Subject: Re: FVWM: can xcompmgr work in fvwm config? On Wed, 6 Feb 2008 00:05:07 +0800 for.register for.register [EMAIL PROTECTED] wrote: I used to xcompmgr in fluxbox, since I can set different alpha value in ~/.fluxbox/init for different transparency. For focus window, transparency can be set to 1%, mean while unfocus windown can set to 90%. My question is can I do the same thing in fvwm under xcompmgr? Thanks for any advice. Walter There are some topics about it in the forums, for example: http://fvwm.lair.be/viewtopic.php?f=33t=1410view=next Search around for xcompmgr and transset-df for more. -- Jesús Guerrero [EMAIL PROTECTED] -- Jesús Guerrero [EMAIL PROTECTED]
Re: FVWM: can xcompmgr work in fvwm config?
for.register for.register [EMAIL PROTECTED] writes: I used to xcompmgr in fluxbox, since I can set different alpha value in ~/.fluxbox/init for different transparency. For focus window, transparency can be set to 1%, mean while unfocus windown can set to 90%. My question is can I do the same thing in fvwm under xcompmgr? I've written it in another thread, so sorry for repeating: I've written a module which does this -- it can be obtained from tinyapps.sf.net. I'm using it ever since I've started using FVWM. -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal mina86 Nazarewicz (o o) ooo +--mina86*tlen.pl--jid:mina86*jabber.org--ooO--(_)--Ooo--
Re: FVWM: can xcompmgr work in fvwm config?
On 06Feb2008 00:37, Michal Nazarewicz [EMAIL PROTECTED] wrote: | for.register for.register [EMAIL PROTECTED] writes: | I used to xcompmgr in fluxbox, since I can set different alpha value | in ~/.fluxbox/init for different transparency. For focus window, | transparency can be set to 1%, mean while unfocus windown can set to | 90%. My question is can I do the same thing in fvwm under xcompmgr? | | I've written it in another thread, so sorry for repeating: I've written | a module which does this -- it can be obtained from tinyapps.sf.net. | I'm using it ever since I've started using FVWM. I expect you can also do it using FvwmEvent, watching the focus change events. -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ It's a vague science. - Rory Tate, circle researcher.
Re: FVWM: can xcompmgr work in fvwm config?
On Wed, 6 Feb 2008 16:15:11 +1100 Cameron Simpson [EMAIL PROTECTED] wrote: On 06Feb2008 00:37, Michal Nazarewicz [EMAIL PROTECTED] wrote: | for.register for.register [EMAIL PROTECTED] writes: | I used to xcompmgr in fluxbox, since I can set different alpha value | in ~/.fluxbox/init for different transparency. For focus window, | transparency can be set to 1%, mean while unfocus windown can set to | 90%. My question is can I do the same thing in fvwm under xcompmgr? | | I've written it in another thread, so sorry for repeating: I've written | a module which does this -- it can be obtained from tinyapps.sf.net. | I'm using it ever since I've started using FVWM. I expect you can also do it using FvwmEvent, watching the focus change events. Probably, I never player with this things. But don't get too happy about xcompmgr. It is old, it is buggy (depending on the options you use) and it doesn't use any hardware acceleration. It will eat your cpu if you need to move a bin window from one page to another. It was just a tool designed to showcase xcomposite, xdamage and all the new technologies that arised in xorg. But it is just that: a toy. -- Jesús Guerrero [EMAIL PROTECTED]
