Re: POLYTEXTOUT problems..( including declarations )
- From: "Mike Williams" <Mike@xxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 11:32:46 +0100
"Mike Williams" <Mike@xxxxxxxxxxxxxxxxx> wrote in message
news:dhtlfn$bcg$1@xxxxxxxxxxxxxxxxxxxxxxx
.. . . oops! I forgot to mention that in order to get the code working I had
to change the declaration to:
Private Declare Function PolyTextOut& _
Lib "gdi32" Alias "PolyTextOutA" ( _
ByVal hdc As Long, _
pptxt As Rum, _
ByVal cStrings As Long)
Having to do such a thing tells me for sure that I am going about all this
in a silly roundabout way, and that there is a far easier way of doing it,
but I haven't had my breakfast yet (slept in late today!). Never much good
before breakfast! (Probably simply changing your existing dynamic array for
a fixed size one will do the trick). Anyway, as I've said, there has got to
be a better way of doing this, but at least the example I posted shows that
the thing actually works ;-)
Mike
.
- Follow-Ups:
- Re: POLYTEXTOUT problems..( including declarations )
- From: J French
- Re: POLYTEXTOUT problems..( including declarations )
- References:
- POLYTEXTOUT problems..
- From: Dan Hinrichs
- POLYTEXTOUT problems..( including declarations )
- From: Dan Hinrichs
- Re: POLYTEXTOUT problems..( including declarations )
- From: Mike Williams
- POLYTEXTOUT problems..
- Prev by Date: Re: POLYTEXTOUT problems..( including declarations )
- Next by Date: HEEEEELP, F1, -- Access violation in Visual Basic
- Previous by thread: Re: POLYTEXTOUT problems..( including declarations )
- Next by thread: Re: POLYTEXTOUT problems..( including declarations )
- Index(es):
Relevant Pages
|