Modify

Opened 12 years ago

Closed 12 years ago

#2378 closed Bug (Fixed)

BITMAPV4HEADER and BITMAPV5HEADER Structures incorrect

Reported by: Ascend4nt@… Owned by: guinness
Milestone: 3.3.9.16 Component: Standard UDFs
Version: 3.3.9.15 Severity: None
Keywords: BITMAPV4HEADER, BITMAPV5HEADER Cc:

Description

In the <WinAPIGdi.au3> header the definitions for BITMAPV4HEADER and BITMAPV5HEADER are incorrect.

For bV4Endpoints and bV5Endpoints, the structure lists these as an array of 3 ints. What it should be really is an array of 9 ints for both.

The relevant links which show the structures:
BITMAPV4HEADER
http://msdn.microsoft.com/en-us/library/windows/desktop/dd183380%28v=vs.85%29.aspx
BITMAPV5HEADER
http://msdn.microsoft.com/en-us/library/windows/desktop/dd183381%28v=vs.85%29.aspx

CIEXYZTRIPLE
http://msdn.microsoft.com/en-us/library/windows/desktop/dd371833%28v=vs.85%29.aspx
CIEXYZ
http://msdn.microsoft.com/en-us/library/windows/desktop/dd371828%28v=vs.85%29.aspx
FXPT2DOT30
No official link on this, but the Windows API has this defined as long in the <WinGDI.h> header:

typedef long            FXPT2DOT30, FAR *LPFXPT2DOT30;

So basically the EndPoints member type is 3 structures of 3 longs, so those arrays needs to be [9].

Change History (1)

comment:1 Changed 12 years ago by guinness

  • Milestone set to 3.3.9.16
  • Owner set to guinness
  • Resolution set to Fixed
  • Status changed from new to closed

Fixed by revision [8418] in version: 3.3.9.16

Guidelines for posting comments:

  • You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
  • In-depth discussions should take place on the forum.

For more information see the full version of the ticket guidelines here.

Add Comment

Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.