public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Syd Polk <spolk@redhat.com>
Cc: Insight Maling List <insight@sources.redhat.com>
Subject: Re: [RFA] libgui/src/tkWarpPointer.c for cygwin
Date: Thu, 03 May 2001 07:03:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0105030659340.26334-100000@ryobi.cygnus.com> (raw)
In-Reply-To: <4.2.0.58.20010502170321.01a43cd0@pop.cygnus.com>

On Wed, 2 May 2001, Syd Polk wrote:

> >+ #ifdef _WIN32
> >+       int wx, wy;
> >+       Tk_GetRootCoords (tkwin, &wx, &wy);
> >+       SetCursorPos@8 (wx + x, wy + y);
> >+ #else
> >+       Window win = Tk_WindowId(tkwin);
> >+       XWarpPointer(Tk_Display(tkwin), None, win, 0, 0, 0, 0, x, y);
> >+ #endif
> >+     }
>
> The second question I have is why do you need "SetCursorPos@8"? Assuming
> you are including winuser.h, you should be able to use "SetCursorPos", and
> either a macro will fix this, or the linker will. I don't think requiring
> the "@8" or "@16" or whatever for Windows API calls is very nice.

I don't need "SetCursorPos@8": I added the header files and forgot to
rename the function in the patch I posted. The actual patch would have
contained a call to SetCursorPos only. Sorry about that.

Keith


  parent reply	other threads:[~2001-05-03  7:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 13:12 Keith Seitz
2001-05-02 17:05 ` Syd Polk
2001-05-02 19:34   ` Christopher Faylor
2001-05-03  7:03   ` Keith Seitz [this message]
2001-05-03 10:48     ` Syd Polk
2001-05-03 10:52       ` Keith Seitz
2001-05-03 10:59         ` Syd Polk
2001-05-04  4:43         ` Insight port to the 'original' Windows Kai Ruottu
2001-05-04  7:05           ` Keith Seitz
2001-05-10  2:27             ` Kai Ruottu
2001-05-17 13:41               ` Keith Seitz
2001-05-03 11:03 [RFA] libgui/src/tkWarpPointer.c for cygwin Keith Seitz

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=Pine.GSO.4.33.0105030659340.26334-100000@ryobi.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=spolk@redhat.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.
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).