- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Thank you both for your replies!
@WCrihfield,
Thanks for the documentation links. I noticed in the Inheritance Basics link there is a notion of a "NotInheritable" Keyword for classes that is false by default, but can be set true. Do you happen to know if Interfaces might have a similar keyword? I couldn't find one in the cursory look through upon reading this post. There is definitely more research to be done on my part.
Have any of the classes you have made been derived from a class that you did not create the base for yourself? Like deriving a class/object from an application specific class/object?
@Frederick_Law,
I intentionally left the idea vague because I don't really know what is even possible yet. I do understand that anything I add will be proprietary to those with access to my add-in, but that is fine with me. Your last statement is roughly what I would like to explore, deriving a part document interface into a proprietary part document interface, to add some custom properties and/or methods.