Re: Isn't WHEEL_DELTA an identifier?

"Robby" <Robby@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Thankyou for your post CARL:
>
>I have gone to your link and I see that there is a table of the prefered
>macros in use by header files. I currently have Windows XP S2 installed in my
>machine which coresponds to the following define statement in this table:
>
>NTDDI_VERSION >=NTDDI_WINXPSP2
>
>and the following table coresponds to the following:
>
>_WIN32_WINNT>=0x0501
>WINVER>=0x0501
>
>Now, when I right click on WHEEL_DELTA in my program it takes me to the
>following definition:
>
>#if(_WIN32_WINNT >= 0x0400)
>/* Value for rolling one detent */
>#define WHEEL_DELTA 120
>#define GET_WHEEL_DELTA_WPARAM(wParam) ((short)HIWORD(wParam))
>
>I don't know what to do.. do I have to change the 400 to 501? or is there a
>setting in the project properties I must change?

The SDK and compiler include files allow you to build programs for any
version of Windows. When you are building a program that you KNOW will be
run on Windows NT 3.51, for example, you want to make sure that you don't
call any APIs that were introduced after that. The include files help you
do that, using the _WIN32_WINNT symbol.

_WIN32_WINNT is a symbol defined by YOU in YOUR project settings (or YOUR
stdafx.h). When you set _WIN32_WINNT to 0x400, for example, you are saying
"I need this program to run on Windows NT 4.0, so please don't allow me to
call any XP-only APIs". If you do not define _WIN32_WINNT, the default
setting hides all of the APIs introduced after NT 3.51.

In your case, you are asking for an API that was introduced in NT 4.0.
Thus, you need to tell the compiler that you need those APIs. To do that,
you have to get _WIN32_WINNT defined to at least 0x0400. One way to do is
to add:

#define _WIN32_WINNT 0x0400

early in your stdafx.h. Another way is to add:

-D_WIN32_WINNT=0x0400

to your project settings.

The NTDDI_VERSION symbol is part of the DDK, not the SDK.
--
- Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
.

Relevant Pages

  • Re: Connecting to the Internet
    ... > APIs was a lot easier than learning Registry APIs.) ... be installed in all versions of Windows that you choose to support. ... I hope you don't mind me saying you have "missed the boat". ... Vague questions such as that are often ignored in Microsoft newsgroups ...
    (microsoft.public.vb.winapi)
  • Re: I really do like OS X but . . .
    ... >features and APIs included in 2000 and XP. ... >still lots of code on Windows that was originally written for Windows ... >> support perspective too. ... which G5s do fairly well at despite the poor optimizations. ...
    (comp.sys.mac.advocacy)
  • Re: Micro$haft desperate! Buy Windoze 7, get (virtual) XP free!
    ... So the Unix certification Apple got is useless, we can tell it's compatible by looking it up in the XCode online help? ... Carbon does have its own graphics layer, but it is QuickDraw and it's deprecated. ... It's especially telling in this case, since doing it this way favored Microsoft Windows: Java on Solaris has to translate to UTF-8, but on Windows it doesn't need to do that. ... But Carbon does have first-class support for Unicode through its upgraded APIs. ...
    (comp.sys.mac.advocacy)
  • Re: Capture ALL movements...event?
    ... your purposes, elements of Windows itself. ... You said earlier "Alternatively some low level APIs might get you there." ... doesn't display when you are using it with Internet Explorer. ...
    (microsoft.public.word.vba.general)
  • Re: Failure of Win API LsaQueryTrustedDomainInfo(..) on a WinNT machine with IN parameter to informa
    ... implemention of the APIs ... Roger Abell ... >> for AD inter-op but this was back when it was still call Windows ... >>> properties on a Win NT PDC machine containing information ...
    (microsoft.public.win2000.security)