Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <20011012032115.16988.qmail@web14502.mail.yahoo.com>
Date: Fri, 12 Oct 2001 13:21:15 +1000 (EST)
From: =?iso-8859-1?q?Danny=20Smith?= <danny_r_smith_2001 AT yahoo DOT co DOT nz>
Subject: Re: w32api maintainer
To: Kim Saunders <kim DOT saunders AT mercuryit DOT com DOT au>, cygwin AT cygwin DOT com
In-Reply-To: <1002851422.786.2.camel@allords>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

 --- Kim Saunders <kim DOT saunders AT mercuryit DOT com DOT au> wrote: > Hi,
> 
> I am using cygwin extensively for a project of mine
> (http://xwinx.sourceforge.net/).
> 
> I am using the w32api code for API calls, but there are a few constants
> that I need that are in the MS platform sdk headers, but not in the
> cygwin w32api headers. For example, the MOUSEEVENTF_WHEEL constant, but
> there are others.
> 
> Who maintains the cygwing w32api code? Who should I be talking to to get
> these constants added, or is there a way I can do it myself?
> 
> Thanks,



Here is where you can submit w32api patches:
https://sourceforge.net/projects/mingw/ 
and click on patches.

But first: Read the license agreement that comes with the MS psdk headers.
It is your responsibilty to understand the terms of that agreement.

Danny



http://briefcase.yahoo.com.au - Yahoo! Briefcase
- Manage your files online.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/