[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuff

From: Eli Zaretskii
Subject: bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuffer frame?
Date: Tue, 29 May 2012 18:44:34 +0300

> From: "Drew Adams" <address@hidden>
> Date: Tue, 29 May 2012 07:12:26 -0700
> Cc: address@hidden
> (That a window manager can accept input passed to a frame that is not on top 
> in
> the stacking order is not exceptional.  That is (was, at least) true for many 
> w.
> mgrs on UNIX, where you could even change the input focus without changing the
> stacking order ("foreground") just by moving the mouse over a lower frame.)

"Stacking order" and "foreground" are 2 different things.  As I wrote
earlier, a "foreground" window/frame is the window that has focus and
gets the keyboard input.  It doesn't have to be on the top of the

> > (let ((old-frame (selected-frame))
> >        (new-frame (make-frame)))
> >    (redirect-frame-focus new-frame old-frame))
> That puts (keeps) the input focus in old-frame.  So it seems to work as it
> should.

No, it keeps focus in new-frame, but makes it so the input you type at
new-frame gets sent to old-frame.  Thus, this:

> (But new-frame has its title and border highlighted as if it had the focus.
> Somehow there is a disconnect between the two.

is normal and expected behavior (AFAIU).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]