On Sun, Aug 11, 2002 at 01:59:08PM -0400, Bob Woodside wrote:
> >     2) ClickToFocusRaises...doesn't. (Reported also by Giuseppe Della
> >     Ricca.) 
> 
>       Still doesn't work.

Fixed.

> However, I notice that MouseFocusClickRaises causes the
> same behaviour expected from ClickToFocusRaises, if you turn on ClickToFocus. 
> In
> other words, MouseFocusClickRaises is behaving like a generic 
> "FocusClickRaises"
> option, and ClickToFocusRaises has no effect.

Yes.  I want to merge the MouseFocusClickRaises and
ClickToFocusRaises options into a single one.  Currently MFCR
activates raising on the client window only and CtFR activates it
on the client window and the decorations.  There is no clean way
to support the old way with separate options easily.  This is
because there is not distinction between all the focus policies
anymore - they are just a set of low level options.

Anyway, should be fixed now.

> >     3) If MouseFocusClickRaises is set and ClickToFocus is also in
> >     effect, mouse clicks don't seem to get through to apps at all.
> 
>       Fixed. But see note on # 2 above.
> 
> 
> >     4) Switching focus options back and forth seems to make some options
> >     suddenly start working that formerly didn't, and others mysteriously to
> >     stop working.

I have cleaned up this mess.  The four basic focus policies should
override each other completely.

> >     5) Some apps have a problem such that when a transient dialogue window
> >     is closed focus does not revert to anyone -- not the transient-for
> >     target(which it used to do), not the last focused window (which it used
> >     to do even further back in history), not anyone. I'm seeing this with
> >     nedit (e.g., the "Search" dialogue), and haven't looked too much
> >     further; so it may be a Motif-specific (or even XtLib) thing (I don't
> >     see it happening with sylpheed, which is Gtk).

Fixed.

Overall, 80% of the bugs are just the wrong default settings.  We
haven't found much problems in the logic itself yet.  By the way,
is the obnoxious xfm/doubleclick problem gone?  I don't have the
proper xfm version to test this.  All the decisions about grabbing
are centralised in focus.c.  So even if it's still there, a fix
will probably be very easy (just calling one of the focus_grab_...
functions at the right place).

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-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to