all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Do Re Mi (was: Q on Text Properties popup menu-shouldn'titusethepointerposition, not the cursor position?)
Date: Wed, 29 Jun 2005 07:52:06 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAEPNCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1DnTjE-0006k7-Dn@fencepost.gnu.org>

    	Also, in some cases it might be
    	good to map two dimensions of the color space at a time,
      not just one.

        It could be done, I suppose. But, unless you would limit
        that to 45 degree
        diagonals (equal changes in two dimensions), which is not
        that useful,

    I think we are miscommunicating.  I'm thinking that horizontal arrows
    could alter one dimension in color space, while vertical arrows
    could alter another dimension.

    Since it doesn't have to be limited to arrows, another pair of keys
    could move in the third dimension of color space.

You can only press one arrow at a time (you can press two, but only one
takes effect).

Using modifier keys it would be possible to truly alter two dimensions at
once, but only in equal (or predefined, constant) proportions. You could
assign any key sequence to such a predefined change, of course.

To allow altering more than one dimension at the same time, in varying
proportions, you need more graphic input - a la the Word dialog box.

Currently, in the doremi color commands, you use up and down arrows for each
color component (no matter which component), and just type [rgbhsv] at any
time to change to a different component. E.g. r up up g down down b down up
up v down down. Simple.

To respond to your suggestion, it would be possible to change things so that
you could use up/down for, say, red, left/right for, say, green, and two
other keys for blue. The (small) advantage is not having to type a `r', `g',
or `b' to switch between components.

That is what I do, for instance, for the doremi frame movement and resizing
commands. In that case, there is a natural association between left/right
arrows and horizontal movement or resizing, and similarly for up/down &
vertical.

For color components, I don't see the advantage of not having to specify the
current component [rgbhsv] outweighing the confusion of keeping straight
which component corresponds to which keys. And, since there are two color
models (RGB & HSV), you would need six key-pair assignments, or you would
still need some way to switch between the models (RGB vs HSV).

        To change more than one color component at the same
        time, it's better to have an interface that shows a color
        space, such as in the Word dialog box.

    That sounds plausible.  I wonder if that could be programmed in Emacs
    Lisp.  Also, some toolkits may have a widget for doing this job,
    and maybe Emacs could invoke it somehow.

Those are things to explore. Bob Chassell suggested using existing Gimp code
that does this kind of thing. Otherwise, it could be done in Lisp, I'm sure,
using small colored characters as the tiny color swatches (no need for
graphics) - a block character could be used.

  reply	other threads:[~2005-06-29 14:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 15:25 Q on Text Properties popup menu - shouldn't it use the pointer position, not the cursor position? Drew Adams
2005-06-24 15:58 ` Luc Teirlinck
2005-06-24 16:37   ` Q on Text Properties popup menu - shouldn't it use the pointerposition, " Drew Adams
2005-06-24 16:48     ` Drew Adams
2005-06-24 23:08     ` Luc Teirlinck
2005-06-24 23:35       ` Q on Text Properties popup menu - shouldn't it use thepointerposition, " Drew Adams
2005-06-25 22:53       ` Drew Adams
2005-06-25 23:17         ` Luc Teirlinck
2005-06-25 23:32           ` Q on Text Properties popup menu - shouldn't it usethepointerposition, " Drew Adams
2005-06-25 23:29         ` Q on Text Properties popup menu - shouldn't it use thepointerposition, " Luc Teirlinck
2005-06-26  1:26         ` Q on Text Properties popup menu - shouldn't it usethepointerposition, " Drew Adams
2005-06-26  1:29           ` Drew Adams
2005-06-27  0:07           ` Q on Text Properties popup menu - shouldn't itusethepointerposition, " Drew Adams
2005-06-27  0:46             ` Drew Adams
2005-06-27 16:46             ` Richard M. Stallman
2005-06-27 22:35               ` Q on Text Properties popup menu - shouldn'titusethepointerposition, " Drew Adams
2005-06-27 22:41               ` Do Re Mi (was: Q on Text Properties popup menu - shouldn'titusethepointerposition, not the cursor position?) Drew Adams
2005-06-28 18:43                 ` Do Re Mi (was: Q on Text Properties popup menu -shouldn'titusethepointerposition, " Drew Adams
2005-06-28 18:47                 ` Do Re Mi (was: Q on Text Properties popup menu - shouldn'titusethepointerposition, " Richard M. Stallman
2005-06-28 19:53                   ` Do Re Mi (was: Q on Text Properties popup menu -shouldn'titusethepointerposition, " Drew Adams
2005-06-28 20:33                     ` Robert J. Chassell
2005-06-28 21:01                       ` Do Re Mi (was: Q on Text Properties popup menu-shouldn'titusethepointerposition, " Drew Adams
2005-06-29  0:42                         ` Robert J. Chassell
2005-06-29  3:59                     ` Do Re Mi (was: Q on Text Properties popup menu -shouldn'titusethepointerposition, " Richard M. Stallman
2005-06-29 14:52                       ` Drew Adams [this message]
2005-06-24 16:09 ` Q on Text Properties popup menu - shouldn't it use the pointer position, not the cursor position? Luc Teirlinck

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=DNEMKBNJBGPAOPIJOOICAEPNCJAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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.