#UE4 OS user names are now sent when the user consents to sending log information. The log has this information in it and the implications are made clear in the UI
#rb Michael.Noland, Matt.Kuhlenschmidt
--------
Integrated using branch Ue4-To-UE4-Fortnite-Simple (reversed) of change#2685578 by Bob.Tellez on 2015/09/09 18:57:49.
[CL 2685579 by Bob Tellez in Main branch]
#UE4 Unattended CrashReportClient now defaults to send log file and personal information if no configs are present (like in thin dedicated server builds).
#RB ben.zeigler
#codereview Jaroslaw.Surowiec
--------
Integrated using branch Ue4-To-UE4-Fortnite-Simple (reversed) of change#2670208 by Bob.Tellez on 2015/08/26 18:33:42.
[CL 2670224 by Bob Tellez in Main branch]
Major changes:
- The widget reflector UI now uses tabs. The hierarchy and stats views have been moved to tabs, and new tabs have been added to support picking widgets from a snapshot.
- The widget reflector node trees are no longer using UObject types. The idea here was to make the serialization easier, but it didn't work and I ended up using JSON instead.
- When you take or load a widget snapshot, you're now shown the screenshot of the window associated with that snapshot, and are able to pick widgets from it as you would do with a live tree.
API changes:
- The tab spawners for the widget reflector and atlas visualizers are now registered automatically when the SlateReflector module is loaded. These are now the only way to create these windows.
- The tabbed layout within the widget reflector has made it impossible to create the widget reflector unless spawned via a tab manager. To this end, the following functions have been removed from ISlateReflectorModule:
- GetWidgetReflector
- GetAtlasVisualizer
- GetTextureAtlasVisualizer
- GetFontAtlasVisualizer
- These functions used to be used to create a raw widget reflector or atlas viewer widget.
- If you were doing this because you were placing it into your own window, you can take advantage of the fact that the widget reflector tab spawner is always available, and use the global tab manager to create your window and place a spawned widget reflector tab inside it - SummonPerfTestSuite in SPerfSuite.cpp provides an example of this.
- If you were doing this in the handler of your own widget reflector tab spawner, you can either just use the standard widget reflector tab spawner instead (you need to load the SlateReflector module once, and then "WidgetReflector" will be available to spawn via the global tab manager), or you can just use the DisplayWidgetReflector function of ISlateReflectorModule (which will internally do the same thing).
[CL 2661609 by Jamie Dale in Main branch]
Changed everything using SlateReflector to list it as a dynamic dependency. Nothing should ever need to link directly to SlateReflector as it just provides an interface for spawning the various debug UIs, such as the WidgetReflector.
Went through and made sure that the Engine/Runtime modules that use SlateReflector aren't using it in a shipping build. Also removed the testing code from AppFramework, and made sure that you can't try and spawn the test suite in a shipping build.
[CL 2660803 by Jamie Dale in Main branch]
I think MainFrame can normally assume that generic commands have been registered by slate application but not in the case of a cook
#jira UE-17346
[CL 2621812 by Matthew Griffin in Main branch]
