I have a unit where there are no blue dots. Furthermore, at run time you
can't set break points in this unit and viewing the stacktrace will
never show any lines from that unit. Stepping through code always skips
that unit as well (the code is ran, it just won't stop there).

It wasn't always like this, but we can't figure out what we've changed.
It's a large unit and I wonder if we've hit some limit somewhere in Delphi.

Any suggestions?

We're on D5

news:4358efe3$1@newsgroups.borland.com...
Chances are you've got a version of that unit open in the IDE which is not
the one that is really part of the project.

--

Download the latest draft (version 1.23, updated 10/2/2005) of
'STILL CASTING SHADOWS: Two American Families 1620-2006'
by Blackbird Crow Raven: http://cc.borland.com/ccweb.exe/listing?id=23106

I wish it were that simple. This problem has been going on for over a
year now. We've hunted for missing CR LF's and other invalid characters.
We've tried everything we can think of.

Is the source code for the blue dots included with Delphi?

Have you tried deleting .tds file, precompiled headers and then doing a
build.
Alternatively, is that unit's directory in debug path (Tools-Options)
HTH Pete
news:4358fa14$1@newsgroups.borland.com...

Since this started we've built three new machines and the problem exists
on them as well. The only thing similar between them are the pas, dfm,
and dpr files. Everything else we let Delphi create.

1. I don't have a tds, blowing the dcu's aways doesn't help. I don't see
a debug path anywhere, but it is in lib path. Other units in the same
folder work just fine.

It feels like a limitation in Delphi somewhere.

After searching QC it feels like issue 6235. I really hate this problem
and wish Borland would do something about it.

Don't have them.. thanks though.

Hi,

Do you have
{$L-} or
{$LOCALSYMBOLS OFF}
defined in the .pas files?
If so, this will turn off debugging for that unit.

Cheers,

Chris

Ok, I just wiped out the entire implementation section, then did a
Shift- Ctrl- C to let Delhi recreate everything. I still don't have any
blue dots.

The only thing different is that the single blue dot that I had on the
very last 'end' is gone. I didn't mention that dot before because I
didn't think it important.

Anway, does it this mean it's the interface? Could it be the DFM somehow?

Try Following... not sure if it will work...

1 Check that dfm is in Text mode
2 Copy all Source of the unit into a new file into a text editor (for
example notepad)
3 Get the Source view of the form and copy it also to another file to a
text editor
4 make a backup copy of the dfm an pas file.;-)
5 delete the dfm and pas file
6 create the pas and dfm manually and paste code and dfm into the
correct place..
7 cross fingers and look after compiling if the blue dots appear
again... :-)

Once this happened to me and I found that a special char was mixed in
the source, it was
not visible at the IDE Code Editor but I could see it with a Hex editor..

I hope this solves you the problem..

Regards,
John

It's somehow related to my TTables and persistent fields.

I've created a new project and copied over every non visual control from
the affectd unit. Compiling this unit shows there are no blue dots. As I
begin to drop tables I hit a magic point at which the blue dots show up.
I can get this down to a removing a single field. Adding the field back
in causes the dots to dissappear, where as removing it causes the dots
to appear.

Sounds like a DM can only have so many persitant fields. To test that I
created another DM and copied over my biggest table. Then I copied it
numerous times until I was well past the total number of fields in the
srouce DM. It still has blue dots.

Then I copied in some of the other tables and I finally lost my dots. So
it seems to be the product of fields from different tables. Does Delphi
know that I was copying the original table a bunch of times and then did
some compiler magic that made them all the same or somthing?

Any ideas? What's the pattern?

may I suggest that with fields missing you could not cleaning compile
your code so - - no blue dots - - which show up in the source code after
the code is cleanly compiled. Adding the fields back in - - the code
would compile cleanly.

I found doing not just a build but a build project tends to clean this
up and has been mentioned in the past year by others in this newsgroup.

Also I have heard that people found out that an old/other version of the
source code was having it's DCU being used and not the *.pas file they
thought they were using. So of course the blue dots can not show up - -

This tended to be a library path issue most of the time.

Jim P.

'Jim P' <Ji...@mad.scientist.com> wrote

Try Preston's source code from the zip in attachments
(Missing Blue Dots project) yourself. I can reproduce
his problem. Regards, JohnH

'preston' skrev :

Same kind of limitation in D2005
I tested the attached project and no blue dots,
except for the last line.

/ia

'Ingvar Anderberg' <whate...@foundit.com> wrote

Ingvar,

Would you be so kind as to add your comment to
Preston's QC report 20462.

If I am reading the related QC report 7358 correctly, then
at least some of the 'missing blue dots' problems may
be fixed in the future Dexter product.

--

Thanks, JohnH
Quality Central, bug status & reporting http://qc.borland.com/
QC discussion is in newsgroup 'borland.public.bdn.qualitycentral'.