Users can now choose a set of relevant units to display applicable properties in.
Setting a single unit for a given type will result in only that unit ever being used. When multiple exist, the most appropriate unit will be shown when a property editor is opened, and will remain in this unit until something else is selected.
[CL 2519064 by Andrew Rodham in Main branch]
Made sure everything was using FText rather than FString, and also updated the property editor API to return tooltips as FText rather than FString.
[CL 2373917 by Jamie Dale in Main branch]
The display name, filter string, and tooltips for the property editor (and associated detail customizations) are now stored as FText rather than FString. This allows us to remove SLATE_TEXT_ARGUMENT from the detail customization widgets.
[CL 2372595 by Jamie Dale in Main branch]
The default (6 digits after point) string representation of float is used in PropertyEditor. It's the highest exact precision, and it's used everywhere else in the code.
ttp 346819 Cannot recompile a blueprint
The issue was introduced in cl#2228482
#codereview Thomas.Sarkanen, Nick.Whiting
[CL 2306818 by Ben Marsh in Main branch]
OnlyPlaceable metadata added. Indicates whether only placeable classes should be shown in the class picker.
More robust AGameMode::PreInitializeComponents
ttp345655 CRITICAL: CRASH: BLUEPRINT: adding GameMode blueprint as a child actor
[CL 2295026 by Maciej Mroz in Main branch]
Fix crash when replacing material in the "New Landscape" panel with one with fewer material layers (or null)
Fix undo transactions for "interactive" changes (e.g. sliding sliders) so they don't flood the undo buffer with one transaction for every sub-step of the change
[CL 2256153 by Gareth Martin in Main branch]
- Added ability to key into UMG animations via the details panel
- Fixed some undo/redo issues in sequencer related to autokey
- Fixed auto-key causing property migration
[CL 2231142 by Matt Kuhlenschmidt in Main branch]
Made sure to call NotifyFinishedChangingProperties so that packages are dirtied when editing values.
Also increased precision in floating-point SetValue. We should not go via strings to do this, but we dont have any other way at the moment, so this is the next best thing.
TTP# 341202 - BLUEPRINT: A transforms default value does not get carried over from the set values in its structure
reviewed by Andrew.Brown
[CL 2228482 by Thomas Sarkanen in Main branch]
