Tile Set Editor: Switched how the per-tile properties are being customized to avoid staleness when the # of tiles changes
Tile Set Editor: Fixed the display of the dimensions (in tiles) in the header to show the correct number
[UE-14703]
#codereview matt.kuhlenschmidt
[CL 2530895 by Michael Noland in Main branch]
- Fixed memory leaks with property buttons keeping property nodes alive
- Fixed the browse button not being used when an property is edit const
[CL 2521486 by Matt Kuhlenschmidt in Main branch]
We now have the capacity to set a uproperty value anywhere in the config file hierarchy
Satisfies UEPLAT-429
The user can now use the 'ConfigHierarchyEditable' meta flag in their uproperties to present a butoon that allows the property to be edited in the config hierarchy, where applicable.
Target platform is configurable.
[CL 2521330 by Terence Burns in Main branch]
Previously you could only control whether you saw object properties or not, you can now control whether you see object, asset, class, and interface properties.
[CL 2520833 by Jamie Dale in Main branch]
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]
Newly installed versions of the engine will now attempt to copy the project-agnostic config settings from a previous engine installation. This happens by way of a versioned manifest that copies old versions when the manifest does not exist, or is a different version. This code path is benign for non-installed versions of the engine (or FPaths::ShouldSaveToUserDir() is false).
EditorGameAgnosticSettings and EditorUserSettings ini paths have been renamed to EditorSettings and EditorPerProjectUserSettings respectively to better convey their purpose. In general, most settings should be saved in EditorSettings (project-agnostic) so that they apply regardless of which project is open. We have some way to go migrating existing settings for this to be the case, however.
Some previously per-project configuration files are now project-agnostic (such as Editor.ini, EditorKeyBindings.ini, and EditorLayout.ini)
GEditor->Access...Settings and GEditor->Get...Settings have been removed in favor of direct access of the CDO through GetMutableDefault<> and GetDefault<> respectively. Global config ini filenames that are not set up are now neither loaded nor saved on build machines, to handle the problem of indeterminate state more generically.
This addresses UETOOL-270 (Most editor preferences should be project-agnostic)
[CL 2517558 by Andrew Rodham in Main branch]
