Component Storage Mechanism
Posted on 1997-09-27
I have a problem that seems to lie with the mechanism that Delphi uses to store the representation of components. I am attempting to use an existing components source as the basis for a new component I wish to develop. Inheritance is not appropriate as I am going to be making substantial
numbers of amendments to the functionality, but the source solves a lot of development issues I would otherwise have. I have taken these steps as a start point:
1 I set up a new component (with appropriate name changes) inheriting from the parent of the component I wish to copy.
2 copied the source of the component
3 Written a registrtion unit, again copying the source relevant to that I wish to use, and registered the copy.
4. Because of the problems I am having I have checked the (60 page) source line by line and am confident that it is identical to the original.
At this stage the component should be identical to my source (except for name). The component appears to work correctly in design mode (except for some property editors I have not yet copied). When running the component
part of it (the tabs in a tabbed notebook) get duplicated. The problems arise when ReadState is called, and appear to be related to the storage of information as the duplication is reflected in the Object Inspector. The other characteristic of the copy and the original that differs is that when viewing a form as tezt the original places comparatively little information, while the copy places a great deal of information in the text file (including full details of constituant components which do not written out in the original).
Can anybody provide assistance as to how to tackle identifying and isolating this problem.