Ok, maybe I´m missing something here. Take a look at this code:
procedure TGDICanvas.DoFillTriangle(const P1, P2, P3: TPoint);
var
pts : array[1..3] of windows.TPoint;
pt: TPoint;
begin
pt := Transform(P1);
pts[1].X := pt.X; pts[1].Y := pt.Y;
pt := Transform(P2);
pts[2].X := pt.X; pts[2
I'm using Lazarus to do an application for WinCE that takes data from a
local mysql database.
Doing the GUI staff was not hard, and i still didn't see any differences
between wince and win32, except for some bug or "special functions" like
the drag&drop on TLists objects that i wanted to use (
2007/1/7, Aleš Katona <[EMAIL PROTECTED]>:
On Ne, 2007-01-07 at 00:23 -0200, Felipe Monteiro de Carvalho wrote:
> Hello,
>
> I am porting fpgfx to Windows CE. During this work I noticed a lot of
> incompatibilities between win32 windows unit and wince windows unit.
> Trivial stuff, like a parame
> > wince.
> >
> > Is there any special reason why it?s like that? Should we try to get
> > both units as compatible as possible? Can I send a patch for that?
>
> I'm not an expert on the windows unit but I encountered similar problems
> among platforms and I think we should defenetly go for comp
On Ne, 2007-01-07 at 00:23 -0200, Felipe Monteiro de Carvalho wrote:
> Hello,
>
> I am porting fpgfx to Windows CE. During this work I noticed a lot of
> incompatibilities between win32 windows unit and wince windows unit.
> Trivial stuff, like a parameter is var on win32, but is a pointer on
> wi
Hello,
I am porting fpgfx to Windows CE. During this work I noticed a lot of
incompatibilities between win32 windows unit and wince windows unit.
Trivial stuff, like a parameter is var on win32, but is a pointer on
wince.
Is there any special reason why it´s like that? Should we try to get
both
