Previously, all pathway code was based on the abstract class "Pathway." Because it is an abstract class, rather than an interface, it made it difficult for objects that already derive from another class (e.g. MonoBehaviour) to provide pathway information.
Switching to an interface allows those classes to implement the required methods without losing their existing base class relationship; and because the Pathway class itself supports the interface, no existing code should be affected.
Previously, all pathway code was based on the abstract class "Pathway." Because it is an abstract class, rather than an interface, it made it difficult for objects that already derive from another class (e.g. MonoBehaviour) to provide pathway information.
Switching to an interface allows those classes to implement the required methods without losing their existing base class relationship; and because the Pathway class itself supports the interface, no existing code should be affected.