[DUG] Oddity with uses clause in D2006

[John Bird]

Yeah me too...

Recompiling a few times sometimes fixes it...and its intermittent, not
consistent.  I can understand it in the sense there are 2 virtually
independent compilers at work, the real time one which is a bit flaky and
the real one which is fine.

When it works properly, which is 90% of the time it's a terrific feature,
immediate feedback on whether the current unit is missing a declaration or
something in its use clause...

John


-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz] On
Behalf Of Conor Boyd
Sent: Wednesday, 12 July 2006 11:43 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: RE: [DUG] Oddity with uses clause in D2006


Yup, I get it as well.

I tend to find a full compile (and sometimes reloading the project as
well) fixes it most of the time, but it's a bit of a PITA nevertheless.

Cheers,

C. 

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of Phil Scadden

fairly trivial but I am finding certain units are underlined in red my uses
clause, saying it cant resolve them. In fact, some of them are part of the
project and the compiler has no trouble at all. However code insight cant do
anything with classes in these units. Anyone else see this? Any idea of
solution? I cant see why one unit is seen but another in identical location
is not.

_______________________________________________
Delphi mailing list
Delphi at ns3.123.co.nz http://ns3.123.co.nz/mailman/listinfo/delphi


__________ NOD32 1.1461 (20060329) Information __________

This message was checked by NOD32 antivirus system. http://www.eset.com