Possible misprint in help file ?


Author
Message
Charles R Hankey
Charles R Hankey
Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)Advanced StrataFrame User (940 reputation)
Group: Forum Members
Posts: 524, Visits: 30K
From Help

Note: The IPopulateOnFormLoad interface inherits from IInitOnFormLoad.  Therefore, whenever this page discusses a member of the IInitOnFormLoad interface, that member belongs to both interfaces.  A class does NOT need to implement IPopulateOnFormLoad if it implements IInitOnFormLoad.

Since the iPopulateOnFormLoad inherits from IInitOnFormLoad I get why you wouldn't need to implement the parent class if the inherited class - which included all of its functionality - was implemented  But I don't get why the reverse - as shown in the Help - would be true.

Is this a misprint or am I misunderstanding inheritance in .NET ?

TIA

Charles

StrataFrame Team
S
StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)StrataFrame Developer (4.4K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
Nope looks like a misprint... If you've Implemented IPopulateOnFormLoad, you won't need to implement IInitOnFormLoad but the opposite is not true.  Like the old logic:

(If P -> Q) then (If ~Q -> ~P) is proper, but (If ~P -> ~Q) is not proper.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search