When deriving from a base class which defines BlueprintCallable functions, I’d like the option to specify parent functions which should be hidden on objects of the child class.
I’ve noticed that the HideCategories metadata will do this, but only for the context menu that appears when inside a blueprint deriving from the child class. Contexts menus in other blueprints, when dragging off an object of the child class, will still show functions in hidden categories. Ideally, it would also be possible to hide specific functions by name, rather than category.
This is a very old feature request, but I’d like to revitalize this, and to include c++ as well. The only way I’ve found is to manually = delete; each parent class function in the base class we create. It would be nice to have a simple flag that will prevent a user from being overloaded by all the functionality of the inheritance tree for their derived class, except what’s specified (such as pure virtual functions).
I’m meaning higher up in inheritance, like if I created a component from actorcomponent, I’d like to be able to hide all functionality for actorcomponent that won’t be relevant to the user of my component.
So that if they create a derived component, when they go to access/override functionality they aren’t met with a wall of different functions and are unable to find what I’ve specifically created for them.