>>>Sysmetric() maps to the 16bit Win API, the Taskbar info was added in the Win32 API. They probably won't update it because they made it so easy to call the API directly.
>>
>>Hi Albert,
>>
>>Let's clear this up so that no one misunderstands what's said here. VFP isn't calling a 16 bit function. It's calling GetSystemMetrics() in USER32.DLL. This function, however, was available in Win16, and FPW called that one.
>>
>>Unfortunately, from my POV, the parameters to SYSMETRIC() don't directly correspond to those passed to GetSystemMetrics(). For example, the screen width in SYSMETRIC() is 1, in GetSystemMetrics() you use 0.
>
>Of course it is, the problem is that it is only passing the parameters the apply to the 16bit version.

If you aren't happy with it, you can call GetSystemMetrics yourself Albert - not a difficult structure. If they were going to expose part of the API, there are a whole lot of things I'd put far ahead of the system metric information because of the relative difficulty of accessing them.