These methods are used throughout the widgets as new code is needed to be placed in certain spots of the objects initialisation. In the beginning, these are blank to allow for each type of object to inherit a blank method to begin with. For example, code that needs to be added to the specificCreate method of a DynDocument, is not the same as the code needed for the DynLayer. However, the DynObject still needs this defined because it is executed by the Object's initialisation code. I know this sounds confusing, but I think you are on the right track to making more sense than me : ) [EMAIL PROTECTED] wrote: > Hi all, > > I am still a novice at the DynAPI 2 and have been slowly digesting the code > piece by piece, I noticed in the DynObject code three "empty" functions. > > specificCreate() > specificRemove() > and invokeEvent() > > Can anyone tell me why there is no code defined for them, are they > equivalent to virtual methods in C++ and hence the code is "overidden" in a > "inherrited" object (for want of better words). > > Sid Young > > _______________________________________________ > Dynapi-Help mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/dynapi-help -- Michael Pemberton [EMAIL PROTECTED] ICQ: 12107010 _______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-help
