AutoRequest reference, where am I wrong?

[fstarred]

According to reference, Autorequest routine is so composed:

Response = AutoRequest( Window, BodyText, PosText, NegText,
	D0                      A0      A1        A2       A3
			PosFlags, NegFlags, Width, Height )
			D0        D1        D2     D3

By taking a look to IntuiText struct, it is so composed:

struct IntuiText
{
    UBYTE FrontPen, BackPen;	/* the pen numbers for the rendering */
    UBYTE DrawMode;		/* the mode for rendering the text */
    WORD LeftEdge;		/* relative start location for the text */
    WORD TopEdge;		/* relative start location for the text */
    struct TextAttr *ITextFont;	/* if NULL, you accept the default */
    UBYTE *IText;		/* pointer to null-terminated text */
    struct IntuiText *NextText; /* pointer to another IntuiText to render */
};

So I expect to see LeftEdge value as the 4th byte of the struct;
I then debugged the AutoRequest call on some games, and here's an example of BodyText:

0001CFB0 0000 0000 0003 0003 0000 0000 0001 CF94 
0001CFC0 0001 CF80 [...]

As you can see, the Left Edge starts at 5th byte.
I read many manuals and all give that info about IntuiText.

What's the matter?

[thomas]

A WORD must be at an even address. Because of this the C compiler adds an additional pad byte between DrawMode and LeftEdge so that LeftEdge starts at offset 4.

[paraj]

FYI the Structure offset page of the reference docs is very handy when manually disassembling

[fstarred]

Originally Posted by thomas

A WORD must be at an even address. Because of this the C compiler adds an additional pad byte between DrawMode and LeftEdge so that LeftEdge starts at offset 4.

Oh you are correct sir

FYI the Structure offset page of the reference docs is very handy when manually disassembling

This is absolutely a must, thank u for sharing it