Re: Notification: incoming/876
On Thu, Jun 13, 2002 at 11:56:43PM +0200, Jan Echternach wrote: On Wed, Jun 12, 2002 at 12:02:53AM +0200, Jan Echternach wrote: I've tried fvwm-snap-20020607, and the root colormap is restored properly again. But the old bug is also back: Closing Netscape's Find window with ESC doesn't restore Netscape's colormap if the pointer is inside the Netscape window, but outside the Find dialog. Same with fvwm-2.4.8. I've discovered that HandleEnterNotify() is only called with Netscape's frame window in this situation, not with the real window. Output from a fprintf() at the beginning of HandleEnterNotify(): ewp-window=0x8000a0, Event.xany.window=0x8000a0, Tmp_win-w=0x14003ae If the pointer was inside the transient Find window before closing it: ewp-window=0x8000a0, Event.xany.window=0x8000a0, Tmp_win-w=0x14003ae ewp-window=0x14003ae, Event.xany.window=0x14003ae, Tmp_win-w=0x14003ae If the pointer is moved onto the title bar: ewp-window=0x8000a1, Event.xany.window=0x8000a1, Tmp_win-w=0x14003ae I've no idea what this Tmp_win-frame window is, The frame window is the big window that contains the client window (-w) and all the decorative windows. or why there is sometimes one EnterNotify event and sometimes two. But changing Event.xany.window == Tmp_win-w to Event.xany.window == Tmp_win-w || Event.xany.window == Tmp_win-frame near the end of HandleEnterNotify() seems to fix (or work around) the problem. I'd rather not modify the EnterNotify handling code. It's rather touchy at the moment. And it shouldn't be necessary either. In the situation you describe, no EnterNotify events are generated because the pointer doesn't change windows. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
Re: FVWM: Remember icon placement?
On Wed, Jun 12, 2002 at 02:16:58PM -0600, Steve Talley wrote: Clarification -- Dominik's fix (Set is_icon_moved flag if icon is moved non-interactively.) did make it in to 2.4.8, but the new parameters $[i.x] and $[i.y] which are used below, are only available in 2.5.x. That's right. We don't put new features in the stable releases. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
Re: FVWM: wanted: beos style titlebars
On Wed, Jun 12, 2002 at 03:12:39PM -0400, Stephen Dennison wrote: Would it be possible to use an image in the titlebar, having some transparency on the right side of it, and eliminate the buttons on the right hand side of the window to simulate the desired look? No, not with the current code. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- 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]
FVWM: fvwm hangs
Hello All
If I execute a tcl script from the fvwm menu
that has the the following line:
Tkxset Exec exec /scripts/tkxset
It start up fine and works fine but when I push the quit
button which executes the following tcl procedure
#!/usr/local/bin/wish #- First line of script
..
..
proc quit {} {
destroy .
}
the button stays depressed and the whole root screen partially
freezes. Partially because the mouse is still working, but the
various applications do not respond. (i.e in focus-follows mouse
the xterms dont' change color as I move the mouse into them,
raising and lowering window or moving no longer works etc.)
Now if I'm clever I'll have two xterms
1) with the line: sh-2.05a# ps x
2) with the line: sh-2.05a# kill
I can add a carriage return to the ps x, get the process
number (cut and paste) and add it to the kill and kill the
tk application. It does not kill the application!, or restore
the window manager. Every thing remains non-functional but the
usual sequence cntrl-alt-backspace still works so I can kill
the xserver and start again.
I have the following
(These comments apply to all tk/tcl applications)
1) Start tkset(just a tk/tcl application) from an xterm.
Works fine and exits fine.
2) Start from the root menu and use the window dropdown
...
...
Delete
Close -- this partially hangs the window manager
Destroy -- closes the application
...
...
I'm using
fvwm-2.4.8
linux-2.4.18
xwindows 4.20
glibc-2.2.5
gcc-3.0.4
no gnome
I suspect that the problem is not fvwm but
one of the other major subsystems, but who ?
I've been using fvwm for 5 or 6 years and
this is something new.
Bruce
Ps I'm behind the great firewall of China and if
I subscribe to the list I tend to get weird things
happening like messages from the mailing list saying
that message are bounceing back with headers that say
More than ten words matched. Rejected
so if you could cc any replies it would be appreciated.
[EMAIL PROTECTED]
--
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]
