On Tue, Aug 20, 2002 at 06:02:58PM -0400, Sergey Babkin wrote:
> A separate issue: something wrong seems to be going on with the focus
> on the nested clients (such as a parent Tcl/Tk program providing a frame
> with option -container and a child Tcl/Tk program running within this
> frame with option -use). When the mouse pointer gets moved into the parent
> window and then out of it, the child loses its focus. Since I use
> the mode ClickToFocus, that should not happen (and indeed did not happen
> with fvwm1 nor with CDE WM). This bug occurs both in the latest snapshot
> and in 2.4.8.
>
> Here is a small example of a Tcl script for demonstration:
>
> -------------------------------
>
> #!/usr/local/bin/wish8.0
> #
> # test of a client swallowed by another client
>
> puts "swallow $argv"
> if {![string compare [lindex $argv 0] {-child}]} {
> label .l -text "internal" -bg white -fg black
> pack .l
> bind .l <FocusIn> ".l config -bg yellow"
> bind .l <FocusOut> ".l config -bg white"
> focus .l
> } else {
> frame .f -bd 10 -bg blue -relief sunken
> frame .f.f -container 1
> pack .f.f .f
> exec $argv0 -use [winfo id .f.f] -child &
> bind .f <FocusIn> ".f config -bg red"
> bind .f <FocusOut> ".f config -bg blue"
> focus .f.f
> }
> -------------------------------
>
> (you may need to edit the interpreter path according to where you have
> wish on your system). It contains two window one in another. The outer
> (frame) window is blue when it does not have focus and red when it
> has focus. The inner window is white when it does not have focus and
> yellow when it does. The outer window is hardwired to pass the
> focus to the inner window whenever it receives the focus.
> Normally the only possible color combinations should be "red-yellow"
> and "blue-white" (well, except after the initial start before the focus
> gets switched for the first time - it's an independent Tk issue). However
> with fvwm2 many more strange combinations happen.
The application is lieing about its focus model. It claims that it
never sets the focus itself but still does so. This is a clear
violation of the ICCCM rules. The window *must* set the
WM_TAKES_FOCUS protocol in the WM_PROTOCOLS property and abide to
it. If the problem persists once the application has been fixed,
please report back.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [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]
