From: Joe Matarazzo <joe.matarazzo@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: [PATCH] Feedback request for x_set_mouse_color on NextSTEP/MacOS
Date: Sat, 16 Aug 2014 20:06:59 -0700 [thread overview]
Message-ID: <CANs_5e7itV1_W3kmd-UQ9sQxDYexU=LKTY+OKqmyVpLgU4nuXg@mail.gmail.com> (raw)
In-Reply-To: <5845089A-A99C-4D72-825F-80E8C9136F00@swipnet.se>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Sat, Aug 16, 2014 at 1:52 AM, Jan Djärv <jan.h.d@swipnet.se> wrote:
> Hi.
>
> 15 aug 2014 kl. 20:46 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
>
> >> It is not requred that the same code works on both OSX and GNUStep, but
> that
> >> there is an implementation for GNUStep and OSX. They might be quite
> >> different #ifdef... blocks of code.
> >
> > But if it can be "the same code", it's clearly a better choice.
> >
>
> Yes, but a fast look at the API:s suggests that this is not possible. I
> would like to be shown wrong though.
>
>
I've been having some early success creating a fascimile of the system
cursors by drawing into
a custom image rep and then tying it to a new cursor via
-initWithImage:hotSpot:. I can duplicate
the vector graphics and fill/stroke the paths to the requested colors.
What do you think of this approach?
Joe
[-- Attachment #2: Type: text/html, Size: 1478 bytes --]
next prev parent reply other threads:[~2014-08-17 3:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 18:32 [PATCH] Feedback request for x_set_mouse_color on NextSTEP/MacOS Joe Matarazzo
2014-08-14 6:41 ` Jan D.
2014-08-15 15:28 ` Joe Matarazzo
2014-08-15 16:29 ` Jan Djärv
2014-08-15 18:46 ` Stefan Monnier
2014-08-16 8:52 ` Jan Djärv
2014-08-17 3:06 ` Joe Matarazzo [this message]
2014-08-18 13:04 ` Jan Djärv
2014-08-26 5:48 ` Joe Matarazzo
2014-08-29 15:26 ` Jan Djärv
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='CANs_5e7itV1_W3kmd-UQ9sQxDYexU=LKTY+OKqmyVpLgU4nuXg@mail.gmail.com' \
--to=joe.matarazzo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=monnier@iro.umontreal.ca \
/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.