I plan on using CommonUI for my Widget Blueprints. I already have a bunch of UserWidget (Parent Class) Blueprints created. It seems that CommonUI is already a part of UserWidget (see screenshot below).
Does CommonUI explicitly require CommonUserWidget selected as a parent during creation and do I need to re-parent all of my existing UserWidgets to CommonUserWidget as well?
Hello @corekid96 !
CommonUserWidget adds logic related to UI input and other methods (you can check them in CommonUserWidget.h), but it’s not necessary to reparent all your widgets to that class—only if you need special behavior like input handling.
Also, keep in mind that you need to use activatable widgets for your menus to ensure proper layer functionality.
Perfect. Thanks for all the useful info!
Although in my case it looks like I have to re-parent after all because I intend to use the new input features. Kind of why I wanted to use CommonUI in the first place 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
