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]
#jira UE-7808 - Editor slows exponentially when selecting an instanced static mesh in viewport that has a large number of instances
[CL 2427864 by Richard TalbotWatkin in Main branch]
#codereview Robert.Manuszewski
--------
Integrated using branch Ue4-To-UE4-Fortnite-Simple (reversed) of change#2384498 by Ben.Zeigler on 2014/12/10 17:52:54.
[CL 2384499 by Ben Zeigler 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]
Problem: FPropertyItemValueDataTrackerSlate keeps raw pointer to invalid memory.
Fix: FPropertyItemValueDataTrackerSlate is reconstructed.
It's a temporary fix. FPropertyItemValueDataTrackerSlate should never use raw pointer.
#codereview Matt.Kuhlenschmidt
[CL 2351526 by Maciej Mroz in Main branch]
