This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: _WIN32_IE flag and common controls...
- To: Nirmal Prasad <email@example.com>
- Subject: Re: _WIN32_IE flag and common controls...
- From: John Mullee <firstname.lastname@example.org>
- Date: Mon, 22 Mar 1999 04:50:58 +0100
- CC: email@example.com
- Delivered-To: firstname.lastname@example.org
- Delivered-To: mailing list email@example.com
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- Organization: <http://www.exmachina.net/> Ex Machina Interactive Architects
- References: <000701be73ba$510cfeb0$d96f1e26@np_home_pc>
- Sender: email@example.com
Nirmal Prasad wrote:
> Please let me know what to do about the _WIN32_IE flag.. its bothering me a
> lot....Also i have put in the defines for updown and status bar control.
> /* Up-Down Control */
> #if (_WIN32_IE >= 0x0400) /* IE4.0 ??? */
These APIs, datastructures and #defines relate to extensions to
the win32 api by microsoft which are installed depending on
which version of microsoft internet explorer is installed
on the system. I imagine the compiler is supposed to check
the registry to determine which value to use for _WIN32_IE,
or some such nonsense. Or perhaps a target required
MSIE version must be specified when building a binary.
As they don't actually form part of any recognised w32
api, but instead relate to the dubious and creaky
practice of changing the OS APIs when installing
applications, I suggest leaving it out....
But if you go by MS's insistence that MSIE is actually
a _part_ of the operating system, then they should
If this sounds grotesque, unbelievable, bizarre, or
unprecedented, that's okay; it is.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org