|
|
|
|
|
Delphi 5 |
|
|
|
|
If it was not detected as a project then you would not have many of necessary Run menu item enabled so you can't run the second instance of Delphi. The work around for this is to create a Project Group and place the Package inside it. The Delphi 5 always seemed to detect the Package in the Project Group as a true Project. To know if the IDE is detecting the Package as a true runnable Project look at the Caption of the IDE main window. If it is loaded then the Package name is shown in the Caption bar. |
|
|
Delphi 6 |
|
Delphi 7 |
|
"In D7 if you compile the designtime package that contains the
form descendant and the call to RegisterCustomModule you will not be
able to visually design open modules of forms (or datamodules) that
descend from the class the custom module was registered for after the
package has been "Yes. It happens to me when I am working on a project group containing a designtime package and an application and I compile the package after having opened modules from the application." |
|
|
Last Modified on: |
Tips on Debugging a Wizard or Component Package
Delphi 5 could be difficult to debug a package because of an apparent
bug that would not allow the IDE to believe the *.dpk file was
actually a project.