DTMultiWindow UE UMG Multi -window plug -in description

简介: DTMultiWindow UE UMG Multi -window plug -in description

Step of operation:

1. Create a new UMG, select DT User Widget

2. Use the traditional method to build this UMG control.

3. Use the creation window and display



DT User Widget Explanation :

DT User Widget is inherited in User Widget, has all the functions of User Widget, and adds several new blueprint nodes.


Can cover nodes :

On Window Activated :When the window is activated


On Window Deactivated :When the window loses the activation state


On Window Closed :When the window is destroyed and closed


Functional node :

Show Window :Display window

 

Hide Window : Hidden window


Close Window : The window is closed and destroyed


Global blueprint node description:

Create Window



Window is a platform-agnostic representation of a top-level window.

Class : The type of DT User Widget.

Title : Title of the window.

ClientSize : What the initial size of the window should be.

DoModal : Modal window.

Show : Show window.

WindowType : Type of this window.

ScreenPosition : Screen-space position where the window should be initially located.

AutoCenter : The windows auto-centering mode. If set to anything other than None, then the ScreenPosition value will be ignored.

DragAnywhere : The windows auto-ceWhen true, the window can be dragged from anywhere.

IsInitiallyMaximized : Is the window initially maximized.

IsInitiallyMinimized : Is the window initially minimized.

SizingRule : How the window should be sized.

IsTopmostWindow : True if this window should always be on top of all other windows.

FocusWhenFirstShown : Should this window be focused immediately after it is shown?

HasCloseButton : Does this window have a close button?

SupportsMaximize : Can this window be maximized?

SupportsMinimize : Can this window be minimized?

ShouldPreserveAspectRatio : Should this window preserve its aspect ratio when resized by user?

MinWidth : The smallest width this window can be in Desktop Pixel Units.

MinHeight : The smallest height this window can be in Desktop Pixel Units.

MaxWidth : The biggest width this window can be in Desktop Pixel Units.

MaxHeight : The biggest height this window can be in Desktop Pixel Units.


Close All Window

Close and destroy all the currently created windows

相关文章
|
2天前
|
IDE 开发工具 Android开发
Couldn‘t get post build model. Module:UpdateService_0804.main Variant: debugOpen logcat panel fo
Couldn‘t get post build model. Module:UpdateService_0804.main Variant: debugOpen logcat panel fo
18 0
|
10月前
|
Windows
UE DTCmd Plug-in description
UE DTCmd Plug-in description
40 0
|
10月前
|
Windows
DTDragDropFile UE Drag the system file to the window Plug-in Description
DTDragDropFile UE Drag the system file to the window Plug-in Description
44 0
|
JavaScript 前端开发 开发者
Component name “xxx“ should always be multi-word
Component name “xxx“ should always be multi-word
Component name “xxx“ should always be multi-word
SAP WM 为Storage Type 004激活SUM报错 - Storage types without pick-point stor.type require partial pallet
SAP WM 为Storage Type 004激活SUM报错 - Storage types without pick-point stor.type require partial pallet
SAP WM 为Storage Type 004激活SUM报错 - Storage types without pick-point stor.type require partial pallet
|
Android开发
【错误记录】Tinker 热修复示例运行报错 ( patch receive fail: /storage/emulated/0/patch_signed_7zip.apk, code: -2)
【错误记录】Tinker 热修复示例运行报错 ( patch receive fail: /storage/emulated/0/patch_signed_7zip.apk, code: -2)
404 0
【错误记录】Tinker 热修复示例运行报错 ( patch receive fail: /storage/emulated/0/patch_signed_7zip.apk, code: -2)
|
测试技术
SAP IDoc 报错- Function module not allowed SPEIDOC_INPUT_DESADV1 –
SAP IDoc 报错- Function module not allowed SPEIDOC_INPUT_DESADV1 –
SAP IDoc 报错- Function module not allowed SPEIDOC_INPUT_DESADV1 –
SAP WM LPK1 不能把 cross-material control cycles定义成release order parts
SAP WM LPK1 不能把 cross-material control cycles定义成release order parts
SAP WM LPK1 不能把 cross-material control cycles定义成release order parts
|
API
Should we still build application buffer on top of CDS view
Should we still build application buffer on top of CDS view
84 0
Should we still build application buffer on top of CDS view