Regarding the 3dui click event not responding to the bug caused by opening the new interface to hide the previous interface and then closing the new interface and then displaying the original interface...

75ddfb7119b1f72f80c740c9c8943a67.png

bug

The test of this code found that it was executed normally, and the event was also destroyed normally. After I bound the event, I told him that it was normal to destroy it, but why did something go wrong after binding, and finally it was located that as long as the visibility was set to be
able There will be bugs,

UENUM(BlueprintType)
enum class ESlateVisibility : uint8
{
    /** Visible and hit-testable (can interact with cursor). Default value. */
    Visible,
    /** Not visible and takes up no space in the layout (obviously not hit-testable). */
    Collapsed,
    /** Not visible but occupies layout space (obviously not hit-testable). */
    Hidden,
    /** Visible but not hit-testable (cannot interact with cursor) and children in the hierarchy (if any) are also not hit-testable. */
    HitTestInvisible UMETA(DisplayName = "Not Hit-Testable (Self & All Children)"),
    /** Visible but not hit-testable (cannot interact with cursor) and doesn't affect hit-testing on children (if any). */
    SelfHitTestInvisible UMETA(DisplayName = "Not Hit-Testable (Self Only)")
};

I set the display level of the widget inside 3dactor to 999, which is useless.

There is nothing wrong with not modifying the main ui, but I want to hide it because my hands are itchy, because the displayed area is a bit different, and only one area is displayed, but the main ui is often operated, and I cannot destroy it for him.

In the end, there is only one way to realize it.

I just wanted to set its offset (set the position in the viewport), but I found that there is no way to get his original offset.