all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: 19988@debbugs.gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: bug#19988: 25.0.50; Drag events ending in different frame
Date: Mon, 09 Mar 2015 00:34:03 -0400	[thread overview]
Message-ID: <jwvvbiadc6q.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <54FAC7E5.1020604@gmx.at> (martin rudalics's message of "Sat, 07 Mar 2015 10:41:57 +0100")

>> If one of the two is the top window (i.e. the one that's actually
>> visible), then we should use that one,
> Detecting whether "one of the two is the top window (i.e. the one that's
> actually visible)" requires access to the Z order of windows.

Not exactly: since this should be done by the C code, it can ask the
window-system, which is the "current window under the mouse pointer".
The result depends on Z ordering, but Emacs doesn't need to know that
Z ordering.

> The event structure can only contain what we put into it.  Which window
> would you put into this structure after you leave the frame containing
> the window where the start event occurred?

The GUI window that's under the mouse pointer (according to the
window-system).

>> If not, then it doesn't really matter if we "get it right" or not.
> If one frame obscures another, the obscured frame should IMHO not be
> considered a valid target.

If they're both obscured by a third window (which does not belong to
us), then I don't think it matters much either way.


        Stefan





  reply	other threads:[~2015-03-09  4:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 14:30 bug#19988: 25.0.50; Drag events ending in different frame Tassilo Horn
2015-03-03 20:27 ` Eli Zaretskii
2015-03-04  4:28   ` Stefan Monnier
2015-03-04  7:03     ` Tassilo Horn
2015-03-04 17:22       ` Eli Zaretskii
2015-03-04 21:09         ` Tassilo Horn
2015-03-04 22:58           ` Stefan Monnier
2015-03-05  8:05             ` martin rudalics
2015-03-05 17:05             ` Eli Zaretskii
2015-03-05  3:37           ` Eli Zaretskii
2015-03-05  7:19             ` Tassilo Horn
2015-03-05 17:02               ` Eli Zaretskii
2015-03-05 20:07                 ` Tassilo Horn
2015-03-05 20:15                   ` Eli Zaretskii
2015-03-06  7:12                     ` Tassilo Horn
2015-03-06 14:13                       ` Eli Zaretskii
2015-03-06 16:09                       ` Drew Adams
2015-03-06 18:55                         ` martin rudalics
2015-03-05 17:00             ` Eli Zaretskii
2015-03-05 20:01               ` Tassilo Horn
2015-03-05  8:05           ` martin rudalics
2015-03-04 17:19     ` Eli Zaretskii
2015-03-04 15:10 ` martin rudalics
2015-03-04 21:14   ` Tassilo Horn
2015-03-05  8:06     ` martin rudalics
2015-03-06 14:37       ` Stefan Monnier
2015-03-06 18:55         ` martin rudalics
2015-03-06 20:19           ` Stefan Monnier
2015-03-06 21:31             ` martin rudalics
2015-03-07  0:49               ` Stefan Monnier
2015-03-07  9:41                 ` martin rudalics
2015-03-09  4:34                   ` Stefan Monnier [this message]
2015-03-09  7:53                     ` Jan D.
2015-03-09 10:38                       ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvvbiadc6q.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=19988@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=tsdh@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.