Jason P Sage wrote:
The routines I CALL USUALLY have a few variables they use to keep track of
counters or stuff that is only VALID during the life of the Call.
My Problem is sometimes THESE Variables that are local to the sub routines
are getting stomped in longer routines (That perhaps are g
I was wondering the rule on MULTI-THREADING when trying to make something
THREAD SAFE.
I Have multiple threads running, and I MADE EACH have its OWN set of
VARIABLES - so there isn't VARIABLE Stomping from other THREADS.
The routines I CALL USUALLY have a few variables they use to keep track of
Hi,
redef.inc of wince was copied from win32 and almost all redefinition are hidden
by {$ifdef win32}
So compiler only see the following declaration of Polygon in coredll.inc:
function Polygon(_para1:HDC; _para2:LPPOINT; _para3:longint):WINBOOL; external
KernelDLL name 'Polygon';
The compiler
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 (
