On 21 Mar 2003 09:00:56 -0300, Christian Lyra wrote: > > On Thursday 20 March 2003 16:59, Mikhael Goikhman wrote: > > > > Can you strip down the config file to the minimum showing this > > > > behaviour and post it to fvwm-workers, please? > > > > > > I just found the offending part. it's the stroke configuration! > > > If I strip the stroke lines from the config I got the normal > > > behavior... is stroke broken or perhaps maybe my stroke libs? (Debian > > > SID). > > > > We can't know if you don't post your problematic lines (read: we still > > can't reproduce your problem). > > any line that denfines a stroke trigger the problem, like this: > > Stroke N9632147 0 A A Exec exec xterm > Stroke N1475369 0 A A Exec exec netscape > > There's a possibility of my libstroke is broken... but since I only use > it on fvwm and dont even know how to test it!
This configuration (together with "Mouse 1 A A StrokeFunc") does exactly what you explain, I would not say anything is broken. The correct config for what you want is: Stroke N9632147 0 R A Exec exec xterm # draw in root Stroke N9632147 0 W M Exec exec xterm # draw in window with Alt pressed Stroke N1475369 0 R A Exec exec netscape Stroke N1475369 0 W M Exec exec netscape Mouse 3 R A StrokeFunc # use mouse 3 for stroke in root Mouse 3 W M StrokeFunc # use mouse 3 for stroke in window Regards, Mikhael. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
