#preflight 61eefc77ba69a4fdb220bf23
#ROBOMERGE-AUTHOR: marc.audy
#ROBOMERGE-SOURCE: CL 18712765 in //UE5/Release-5.0/... via CL 18712784 via CL 18713147
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v903-18687472)
[CL 18713191 by marc audy in ue5-main branch]
Exposing FPointerEvent to be used in plugins
#rb: Rex.Hill
#preflight 61a67dbb9c77d610077f00b3
#ROBOMERGE-AUTHOR: eric.knapik
#ROBOMERGE-SOURCE: CL 18347364 via CL 18348714 via CL 18348726 via CL 18348732 via CL 18349101 via CL 18349122
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18349127 by eric knapik in ue5-release-engine-test branch]
Refactored the CompositeDragDropOp so that it can be interacted with transparently as any one of its sub ops.
Also now supports Folder Drops in the layer browser
[FYI] max.chen daren.cheng
#rb patrick.enfedaque
#jira none
#ROBOMERGE-SOURCE: CL 14272172 in //UE5/Release-5.0-M2/...
#ROBOMERGE-BOT: STARSHIP (Release-5.0-M2 -> Main) (v724-14254601)
[CL 14272208 by roey borsteinas in ue5-main branch]
#rb Matt.Kuhlenschmidt
#ROBOMERGE-SOURCE: CL 13050736 via CL 13052125 via CL 13052154 via CL 13052198 via CL 13052239
#ROBOMERGE-BOT: RELEASE (Release-Engine-Staging -> Main) (v686-13045012)
[CL 13052261 by nick darnell in Main branch]
#rb [at]Dan.Hertzka
#ROBOMERGE-SOURCE: CL 11294962 via CL 11294963 via CL 11296120 via CL 11296175
#ROBOMERGE-BOT: (v647-11244347)
[CL 11296220 by josh gross in Main branch]
#rnx
#rb none
#ROBOMERGE-OWNER: ryan.durand
#ROBOMERGE-AUTHOR: ryan.durand
#ROBOMERGE-SOURCE: CL 10869210 via CL 10869511 via CL 10869900
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870549 by ryan durand in Main branch]
#jira UE-85456
#ROBOMERGE-SOURCE: CL 10571190 via CL 10571288 via CL 10571294 via CL 10571298 via CL 10571310
#ROBOMERGE-BOT: (v606-10482310)
[CL 10571316 by matt kuhlenschmidt in Main branch]
#rb chris.gagnon
#ROBOMERGE-SOURCE: CL 10541213 via CL 10541286 via CL 10560152 via CL 10560839 via CL 10560958
#ROBOMERGE-BOT: (v606-10482310)
[CL 10561108 by matt kuhlenschmidt in Main branch]
- Resolves issues where the FReply living on ULocalPlayer could cause SObjectWidgets and their associated UUserWidgets to have a delayed destruction process.
- Also just generally stands to reason that if the FReply reference is the only thing keeping a widget alive, there's no chance that SlateApplication will actually be able to do anything meaningful with that widget anyway (it can't be focused, captured, dragged, etc.)
- Resolved a lurking potential crash in FSlateApplication that was made more possible by this change
[at]Nick.Darnell
#ROBOMERGE-SOURCE: CL 10379330 via CL 10380129 via CL 10380157
#ROBOMERGE-BOT: (v594-10333955)
[CL 10380670 by dan hertzka in Main branch]
- Added FSlateUser::IsWidgetInFocusPath() and added some comments explaining the three different functions there for checking focused-ness of a widget
#ROBOMERGE-SOURCE: CL 10282945 via CL 10282946 via CL 10282947
#ROBOMERGE-BOT: (v591-10236483)
[CL 10282948 by dan hertzka in Main branch]
This change makes it possible to remove the layout and painting overhead that Slate performs every frame. The system is off by default as we continue to iterate on it.
However, this includes massive changes to batching, rendering, hit testing, and invalidation panels which are permanent changes and cannot be disabled.
#rb chris.gagnon, nick.darnell
[CODEREVIEW] nick.darnell
#ROBOMERGE-OWNER: matt.kuhlenschmidt
#ROBOMERGE-AUTHOR: matt.kuhlenschmidt
#ROBOMERGE-SOURCE: CL 7232617 via CL 7235502
#ROBOMERGE-BOT: (v367-6836689)
[CL 7235503 by matt kuhlenschmidt in Main branch]
The curve editor supports three view types by default - an absolute view (default, matches old behavior), a stacked view and a normalized view. Stacked views draw each curve separately (so non-overlapping) and normalized against their own min/max values. The normalized view draws all curves overlapping with each one normalized against its own min/max values.
A tree view has been added to help effectively manage large numbers of curves. Selecting curves in the treeview controls which curves are visible in the view area. The treeview also supports pinning curves. These pinned curves will always be visible regardless of your selection in the tree view.
A transform tool and a retiming tool have been implemented (via a plugin) which is enabled by default. The transform tool allows you to do a marquee selection of keys and then translate and scale the positions of these keys. The retiming tool allows you to create a 1 dimensional lattice to adjust the timing of your keys with a linear falloff between each lattice point. These tools work across multiple views at the same time which is especially useful if you are representing one dimensional data (such as event keys) in a view, as it allows you to adjust this data at the same time as your animation curves. A smoothing filter has been implemented (via a plugin) to allow running highpass and lowpass filters on your keys.
Opening the curve editor in Sequencer/UMG now creates a separate dockable tab which can be resized and docked as desired. A time slider has been added to the Curve Editor which is synchronized to the playback time in Sequencer. This allows you to scrub time in the curve editor without having to find the Sequencer window and adjust time there while looking at your keys and previewing your animation in the viewport at the same time.
Rudimentary support has been added for saving and later restoring a set of curves in your current session. This allows you to do a rudimentary copy/paste of entire curves but can also be useful for saving a curve, making adjustments to it and then deciding you want to go back - simply reapply the saved curve! Each curve added supports an intention name (such as "Location.X" or "FieldOfView"), and these intention names will be used when trying to apply curves. This allows you to reliably take all of the curves of a transform on one object and apply them to another object (and ensure that Location.X gets applied to the new Location.X, etc.) this can be helpful if you have a mixed set of curves buffered (such as a location and a field of view). In the event that no curves match by intention you can store and apply a single curve at a time from any intention to any other intention.
The Curve Asset editors (float, vector and color curve assets) have been changed to use the new editor. They support the same treeviews, filtering and tools that the Sequencer editor does. In addition, the Color Curve asset editor adds an additional view which provides a 1 dimensional gradient editor as an easier way to visualize and edit colors instead of the channels individually.
#rb Max.Chen, Andrew.Rodham
#ROBOMERGE-SOURCE: CL 6631811 via CL 6633746
#ROBOMERGE-BOT: (vundefined-6620334)
[CL 6633863 by matt hoffman in Main branch]
marc audy
ben hoffman
eric knapik
daren cheng
Patrick Boutot
roey borsteinas
Marcus Wassmer
nick darnell
Rolando Caloca
josh gross
Juan Canada
ryan durand
matt kuhlenschmidt
dan hertzka
Chris Gagnon
matt hoffman