Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

About Multiple Widgets and UI - whats easier?

I've been pondering restarting my project given I have been phaffing about for 2 weeks on this dilemma... The basic question is what is easier to do: a) Have one HUD/blueprint with ALL of my various UI menu's b) create a separate widget BP for each menu and then call those menus for the button is pressed

My current set up has Game Start screen with separate widgets and options to start new game, load or quit HUD BP with widget for health and stamina etc. AND start menu for calling inventory, equipment and the PC stats sheet Separate Inventory BP to manage the inventory system. I'm have trouble calling the inventory menu up because I cant seem to find a stable variable to call it up Also my code is half in 3rd Person character and half in their own blueprints.

any advice would be appreciated XD

Product Version: UE 4.12
more ▼

asked Sep 24 '16 at 02:03 PM in Blueprint Scripting

avatar image

11 1 1 1

avatar image RuBa1987 Sep 24 '16 at 03:13 PM

In general you should try to make things modular. If you need to copy/paste code around then there is probably a way to abstract it and generalize it.

Personally I would build things one screen at a time and as you notice commonalities between them abstract the code and put it in its own widget. For example, we have some fun things we are doing with buttons so we have a custom button widget that add functionality to the button rather than having to remake the button all the time.

In reality you can do this just about any way you want and it will work but I generally ask myself "How can I code this to make it easier to support?". For me that is the key. Our designers need flexibility and going back to them and telling them it's going to take weeks to make what seems like a simple change is bad. I don't like having to do that because that generally means I made a mistake when designing the system.

These concepts go for all code really but I found it was very important on UIs.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question