Currently the project explorer window only displays class methods that have explicitly been created. I propose a view where classes in the PE window display all the valid methods that can be called on that class. For example, when creating a new ClassB and making it inherit from ClassA, in the project explorer window ClassB is immediately populated with 'shortcuts' to the ClassA methods it can use. These shortcuts are simply a convenience and help with clarity; they don't have any real representation on disk. Dragging a shortcut to a block diagram drops the parent method that shortcut refers to.
Shortcuts need to be distinguishable from real methods in the PE window, so they should be represented by italics or perhaps a unique icon. When ClassB overrides the parent method the shortcut is replaced with the overriding vi. If the parent class has methods that must be overridden the shortcut could be presented in red text or an exclamation point can be laid over the top of the icon in the PE window. Shortcuts to protected methods should include the protected icon.
Classes already contain one "virtual" member--the class .ctl doesn't have a unique representation on disk. In some ways this is an extension of that idea. This also opens the door for desired future extensions to LVOOP, such as traits.
