Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/IDE/Code Completion    [ Add a report in this area ]  
Report #:  9604   Status: Reported
Code Insight Anomoly
Project:  Delphi Build #:  Trial
Version:    9.0 Submitted By:   Liz Kimber
Report Type:  Crash / Data loss / Total failure Date Reported:  11/24/2004 12:13:17 PM
Severity:    Serious / Highly visible problem Last Updated: 6/16/2005 4:54:04 AM
Platform:    All versions Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (2 Total Ratings)
5.00 out of 5
Total Votes: 1
Description
Like many others I have ported over some projects from a previous version of delphi, in my case Delphi 5.

Ive found issues in that the code completion would complain at me that the code was invalid and so couldnt complete the code.  When in fact what it was looking at was the string from the "build with runtime" option, even thoguh it was unselected.

Once this had been enabled, the contents removed as after all vcl50 etc is no longer valid, and disabled once again. The code completer was then able to produced its completions.

Hence suggesting its looking at the runtime libraries, wether you are using them or not. In this case incorrectly keeping the invalid ones from a previous version of delphi.
Steps to Reproduce:
Import a project with some 3rd party apps that you have a new copy of for d2k5, eg say addict spell checker.
go to make a change on the code of the form it will say it cant because it cant use the file say addict3_b5.bpl as its the wrong format - even thoguh the one compiled into d2k5 is not that one as the pathing may show.
Workarounds
enable compile with runtime libraries
remove ALL listed libraries
disable compile with runtime libraries
Attachment
None
Comments

Colin Wilson at 12/22/2004 6:40:09 AM -
I've had exactly the same problem.  Code Insight is using the entries in Project/Options, Packages tab, 'Build with Runtime Packages' - even though the checkbox isn't checked, and the edit box is grayed out.

Once this problem strikes, Code Insight comes up with all sorts of weirdness, including marking packages like Windows, Classes, SysUtils, etc. as 'Could not find package...'

It's a big bad bug, and justifies an A/1 rating.

IMO there's a separate issue here of exactly what is getting added to the edit box there.  For instance, I've had several old Delphi 7 packages being referred to - even then I've never tries to add them to Delphi 2005.

Colin

Colin Wilson at 12/22/2004 6:42:19 AM -
ps.  Liz reports this in the Trial version.  I can confirm that the problem also exists in the release version - 9.0.1761.24408

Colin

Server Response from: ETNACODE01