I need advice about multiple HUDs...

Development Programming & Scripting C++
1

Since my game is a bit complicated 2D RPGs, I may need a various HUDs -> Battle, Dialogues(conversation), and so on.

The problem… is… whether I tried BP or C++, I cannot set specific HUDs as I want.

ClientSetHUD(NewHUDClass); in Player Controller? the problem is… My HUD is the class which being inherited from AHUD, I don’t have any clue (I did googling too) how to convert from my AHUD child class to TSubclassof<AHUD>

Maybe I tried too difficult way. but I don’t want to put every widgets into one HUD, which does not seems right… is it?

p.s. I used to create widgets in PlayerController class… is it correct?

2

some post mentioned don’t use Player Controller to create Widgets… but I also remember that using HUD as storing widgets. I feel complicated… help.

3

I create all my widgets in the HUD and store them there, and use the HUDs Player Controller as the widget’s owner. Generally speaking, a good design is to treat the HUD as a Widget Manager - you should be able to access most if not all of your widgets from there.

You can’t create multiple HUD’s for one player, but you can have as many widgets as you like.

4

Thank you :slight_smile:

Just like you helped me before, I am thinking about ConstructorHelper to get classes of Widget. But Unreal Engine (or Visual Studio) cannot use ConstructorHelper in Constructor function. Even I tried Dynamic Object Loader. everything fails… I am clueless again

5

Don’t use that, you should avoid hardcoded references where you can. Just create UPROPERTY varaibles in your HUD class, and crreate a blueprint-derived HUD and set the widgets. E.g.:



UPROPERTY(EditDefaultsOnly, Category = "Widgets"
TSubclassOf<UUserWidget> WidgetToUse;
6

okay… after that I should initialize them all?

edit. I mean…Creating blueprint derived from HUD class… how do i use them? In BP? or C++ of Player Controller?
I kinda solved it.

7

I like to keep a TMap<FName, TSubclass<UUserWidget>> in my AHUD. Then, I can spawn them by name.

I also keep a TMap<FName, UUserWidget> for the active widgets (on-screen).

Ultimately a very simple API like this one should work fairly straightforwardly.

   UPROPERTY (EditAnywhere, Category = "Custom|WidgetManagement")
   TMap<FName, TSubclassOf<UUserWidget> > WidgetClasses;

   UPROPERTY (VisibleAnywhere, Category = "Custom|WidgetManagement")
   TMap<FName, UUserWidget *> ActiveWidgets;

   TObjectPtr<UUserWidget> GetWidget (FName InWidgetName) const;

   UFUNCTION (Category = "Custom|WidgetManagement")
   void DisplayWidget (FName InWidgetName) const;

   UFUNCTION (Category = "Custom|WidgetManagement")
   void HideWidget (FName InWidgetName) const;

   UFUNCTION (Category = "Custom|WidgetManagement")
   void CreateWidget(FName InWidgetName);

   UFUNCTION (Category = "Custom|WidgetManagement")
   void DestroyWidget(FName InWidgetName);