Session Class Diagram Cheat Sheet

[stepalibre]

These are the most confusing interfaces.

 

[LuminescentLoom]

IADPartSession and IADAssemblySession inherit directly from both IADDesignSession and IADSession, not just transitively? Does that make any difference from the API user's point of view?

 

[stepalibre]

Inheritance adds functionality or combines what's in IADDesignSession and IADSession into IADPartSession.

 

[stepalibre]

Does that make any difference from the API user's point of view?

It does when you're writing code, understanding where methods are and what are the difference between interfaces. There's not a lot of functionality in IADAssemblySession compared to IADPartSession. IADGlobalParameterSession only has two properties and inherits only IADSession.

 

[stepalibre]

Sometimes I forget where a property is. In the Design or the Part and view this Cheat Sheet. I have static classes that wrap a lot of common code, but I review class diagrams, after long periods away from Alibre API projects.

 

[LuminescentLoom]

Inheritance adds functionality or combines what's in IADDesignSession and IADSession into IADPartSession.

Everything in IADSession is already inherited by IADPartSession via IADDesignSession. So I don't think it make a difference for IADPartSession to also inherit directly from IADSession. Or does it?

C# and VB don't even support multiple inheritance, so how is this possible in the .Net API?

 

[stepalibre]

These are interfaces not class:

Public Interface IADPartSession
    Inherits IADSession , IADDesignSession
End Interface
Public Interface IADSession
End Interface
Public Interface IADDesignSession
End Interface

public interface IADPartSession : IADSession, IADDesignSession
{
}
public interface IADSession
{
}
public interface IADDesignSession
{
}

 

[LuminescentLoom]

I see. They really are defined like that for some reason. Maybe it has some subtle effect that matters.

Also TIL multiple inheritance is allowed for interfaces.