Re: Carbon: display-buffer can leave wrong frame with input focus

[YAMAMOTO Mitsuharu]

>>>>> On Thu, 9 Feb 2006 08:58:10 +0000, David Reitter <address@hidden> said:

> Works as intended. The fact that newly opened frames get the focus
> seems inconsistent, however. From a user's perspective, the same
> sequence of inputs will not lead to the same results, depending on
> whether the other frame happens to get focus or not. I think it'd be
> better if the newly opened frame never gets focus - even if the
> window manager initially gives it focus. That would implement the
> documentation of display-buffer more closely: "Make buffer appear in
> some window but don't select it."

Anyway, that's no longer a Carbon-specific issue.  All X11 window
managers that I regularly use behave like this (i.e., a new frame
created by make-frame will get focus).

At least, you can customize the behavior so as not to change the
focus like this:

  (defun my-special-display-popup-frame (buffer &optional args)
    (let ((orig-frame (selected-frame)))
      (special-display-popup-frame buffer args)
      (x-focus-frame orig-frame)))

  (setq special-display-function 'my-special-display-popup-frame)

                                     YAMAMOTO Mitsuharu
                                address@hidden