From: "Jan D." <jan.h.d@swipnet.se>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Drag and drop patch for X, please review.
Date: Tue, 20 Jan 2004 17:24:37 +0100 [thread overview]
Message-ID: <23DA6486-4B65-11D8-91D5-00039363E640@swipnet.se> (raw)
In-Reply-To: <jwvbroyk3z7.fsf-monnier+emacs/devel@asado.iro.umontreal.ca>
>> If the frame is split vertically and text is dropped on the menu bar,
>> there
>> is a bit coordinate calculations to be made to determine which window
>> to use.
>
> I don't know enough to understand I guess. I assume you'd use the same
> kind of code that Kim recently changed to report the full position
> info in
> mouse-click events: this code turns a scren pixel position into a
> bunch of
> "logical position" info: window, buffer-pos, ...
>
> Now, when dropping on the menu-bar, I don't know what DND should do (I
> can't think of any meaningful operation that you could carry this way,
> unless you could drop not just on the menu-bar but on a menu-entry),
> but
> a menu-bar is always linked to a particular window, so getting the
> relevant
> window is a small matter of finding the active window of the frame.
Dropping a file name on the menu bar currently opens the file in a new
window. I think that is useful (i.e. I use it all the time :-)
But the active window is probably not where the drop should go.
Consider
this setup with vertically split windows:
--------------------------------------------
| File Edit Options Buffers Tools Help |
--------------------------------------------
| window 1 |x| window 2 |x| window 3 |x|
--------------------------------------------
|x| represents a scroll bar.
If dropping text onto File, the user might reasonable expect the text
to be pasted into window 1, because it is closest. Dropping on Tools
can be expected to paste the text into window 3.
But the selected window may be window 1, but I think it would be
strange to paste into window 1 when the drop is clearly made closer to
window 3. And what about dropping on the 'e' in Buffers? It is
the same distance to window 2 and window 3. Remember that drag and
drop is very visual, and where the drop does occur is where the action
should happen. To say that the menu bar is associated with window 1
and do all drops there would be confusing for a user.
So while dropping just about anywhere makes sense when used to open a
file, it is more problematic for pasting in text.
Jan D.
next prev parent reply other threads:[~2004-01-20 16:24 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 16:35 Drag and drop patch for X, please review Jan D.
2004-01-17 20:20 ` David Kastrup
2004-01-18 20:22 ` Jan D.
2004-01-18 21:50 ` Kim F. Storm
2004-01-18 21:09 ` Jan D.
2004-01-18 0:40 ` Miles Bader
2004-01-18 20:44 ` Jan D.
2004-01-18 21:34 ` Kai Grossjohann
2004-01-18 21:55 ` Jan D.
2004-01-18 23:08 ` Miles Bader
2004-01-19 20:12 ` Richard Stallman
2004-01-19 20:43 ` Jan D.
2004-01-20 2:34 ` Miles Bader
2004-01-19 20:49 ` Jan D.
2004-01-18 22:10 ` Kim F. Storm
2004-01-18 21:14 ` Jan D.
2004-01-19 18:24 ` Stefan Monnier
2004-01-19 20:47 ` Jan D.
2004-01-19 23:35 ` Jason Rumney
2004-01-19 23:50 ` Jan D.
2004-01-20 15:52 ` Stefan Monnier
2004-01-20 16:05 ` Jan D.
2004-01-20 18:41 ` Stefan Monnier
2004-01-20 20:50 ` Jan D.
2004-01-20 21:12 ` Stefan Monnier
2004-01-20 21:27 ` Jan D.
2004-01-20 22:09 ` Stefan Monnier
2004-01-20 22:28 ` Jan D.
2004-01-20 23:38 ` Stefan Monnier
2004-01-21 21:08 ` Richard Stallman
2004-01-21 22:30 ` Jan D.
2004-01-22 10:19 ` Kim F. Storm
2004-01-22 9:46 ` Jan D.
2004-01-22 11:32 ` Kim F. Storm
2004-01-23 18:25 ` Richard Stallman
2004-01-23 20:05 ` Jan D.
2004-01-24 21:39 ` Richard Stallman
2004-01-18 19:14 ` Richard Stallman
2004-01-18 21:02 ` Jan D.
2004-01-19 20:12 ` Richard Stallman
2004-01-19 21:14 ` Jan D.
2004-01-20 15:31 ` Richard Stallman
2004-01-20 15:49 ` Jan D.
2004-01-21 21:09 ` Richard Stallman
2004-01-21 22:22 ` Jan D.
2004-01-22 19:00 ` Richard Stallman
2004-01-22 19:27 ` Jan D.
2004-01-20 16:02 ` Stefan Monnier
2004-01-20 16:24 ` Jan D. [this message]
2004-01-20 18:43 ` Stefan Monnier
2004-01-20 20:33 ` Jan D.
2004-01-20 20:43 ` Stefan Monnier
2004-01-21 21:08 ` Richard Stallman
2004-01-21 21:14 ` Stefan Monnier
2004-01-21 22:02 ` Jan D.
2004-01-18 19:16 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23DA6486-4B65-11D8-91D5-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).