On Sun, Oct 12, Dominik Vogt, wrote: > I can't reproduce it myself, but it doesn't surprise me. I have > rewritten the focus code recently and that probably plays a role > here.
I'm not sure about that. It was happening a month back, too. (Sorry, I know I'm expected to send a bug report early, but I was trying to be sure if it was a bug.) > Please describe the behaviour as precisely as you can: > > * Just to make sure: did you actually try it with the minimal > config you posted? Yes, I did, with exactly the same config. It still does the same in today's CVS checked out version too. > * What exactly do you have to do to make it happen: > - Where do you press the mouse button? Over the interior of > the window or on some part of the decorations (which part)? > - Where exactly do you move the windows? 1. I setup the config as I said. 2. I start fvwm. The builtin menu is got by right-clicking on the blank desktop. I select the first item, "1. XTerm". 3. I get the wire frame thing which allows me to place the window wherever I want to. I place it near the bottom of the screen. I move the window by pressing Alt and dragging the mouse *inside* the window. The window moves. 4. I do step 3 all over again, but, place the new terminal a little near the top of the screen such that the old one is partly visible. 5. Now, the new window can be moved by Alt + dragging inside the window, but, the old one can't. > * What is the "blinking" effect you see: > - Is the wire frame drawn for a split second and removed > immediately? > - Is the lower window raised and then lowered? > - Or is it a different effect (please describe)? > > * Do you see the move cursor? If not, does the cursor change to > some other icon (which)? I did check the "blinking" effect and it is the visual bell of the terminal. Somehow, instead of the mouse action being interpreted by fvwm, it's being _sent to the terminal directly_. I set the terminal bell in xterm to an audible one and it does beep. No, I don't see the wire-frame nor the move cursor. The lower window doesn't seem to be raised and lowered. Maybe it's too fast for the eyes, but I don't think so. > * Please add any additional information that seems unusual, even > it may seem unrelated. Ok, here's an experiment I tried. After I had the two windows, I closed the top one and the lower one still could not me moved. It just beeped. Here's another minimal config which is interesting: --- 8< --- Mouse 1 W M Raise Key F2 W M Raise --- 8< --- If I have two windows, the clicking on the lower window with Alt pressed down doesn't raise the window, but, Alt+F2 raises the window if it's focused. So, my description of my problem is: As soon as a window goes into the background for the first time, somehow instead of fvwm interpreting mouse actions, it's being sent directly to the app. Ready to give you anymore info. Mail me. If it'd be easier for you if I were on the list, tell me. Also, if none of the Fvwm Workers can reproduce this problem, I'll assume it's a problem on this side. Tell me if it's so. But, I'm pretty sure it's not a problem at this end. I even verified this with two different versions of the X server. Arvind -- It isn't easy being the parent of a six-year-old. However, it's a pretty small price to pay for having somebody around the house who understands computers. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
