[4.9P2][4.8.3] User widget showed incorrectly if take all available space and added as child

№ 6
Title: [4.9P2][4.8.3] User widget showed incorrectly if take all available space and added as child.

Importance: Medium.

Branch: Binary.

Build version:
Version: 4.8.3-2634408+++depot+UE4-Releases+4.8
Version: 4.9.0-2633546+++depot+UE4-Releases+4.9
Version: 4.9.0-2641355+++depot+UE4-Releases+4.9

System Specs:
OS:Win8.
Additional specification will be provided by request.

Attachments:
It will be provided by request.

Detailed description of the issue:
A child widget has various and strange behaviour if a child has an user widget type and anchor set to fill all screen(bottom right corner type).
Most cases a child user widget is not shown on screen. But behaviour depends on engine version and parent widget type.
I have tried to add widget dynamically through “add a child” function and spent some time to understand the reason cause my properly created and visible a child widget wasn’t shown on screen. :slight_smile:

Screenshots/Link to video:
It will be provided by request.

Reproduction steps:

  1. Create a new blank project.
  2. Create a two blue print widgets (widgetA/widgetB).
  3. Add a button to widgetA.
    3.1 Set anchor to anchor16(bottom-right corner).
    3.1 Set all button offset to 0. It takes all widget space.
  4. Add a scroll box to widgetB.
  5. Add widgetA as child widget to the created scroll box and canvas panel in widgetB.
  6. Create widgetB and add it to view port.
  7. Make sure that a child widgetA is not showed for scroll box, but it is exist and it is visible.
  8. Make sure that a child widgetA is showed for canvas panel, but with wrong size.

Frequency: 100%

Expected behaviour:
A child widget takes all available parent space with depending to child aspect ratio or in another case any warning message should be showed.

Hello,

I believe this is working as intended. When setting the anchor points to have the button fill the screen it effectively has no size of it’s own. The Scroll box says for the button to take up as much room as it “needs”. However, the button does not “need” any room because it does not have a size of it’s own. That is why the button takes up 0 space and so it does not render on screen. I hope that this information helps. Thank you for your report.

Make it a great day

Hello, Rudy.
Thank you for your answer with example.
May I ask you one more question?
Where is the sense to allow an user to create a widget that not occupies any space and it does not show at all?

Hello,

My explanation may have been too narrow. The advantage to having a widget without a predetermined size is that it can update dynamically to fit other widgets that may change in size. In the example below I have created a tool tip using an image that is anchored full screen with a text block over the top of it. The image expands and contracts to fit the amount of text applied to the text block. I hope that this information helps.

Example:

This is using the basic setup you mentioned in your opening post

This is a second widget that I have added a copy of the first widget to in order to allow me to use it as a tool tip when needed.

Showing off the re-sizing of the image that is being used as the back ground.