Made placement browser its own tab and not the default mode.
The default mode is now "Select" which does nothing
Modes are now actived from a toolbar drop down (old keybindings still work) and the old tabbed UI for changing modes has been deprecated.
Mode tab no longer appears when there is no active mode and will appear when a mode becomes active
This change resets the default layout of the editor
#rb none
[CL 10286341 by Matt Kuhlenschmidt in Dev-Editor branch]
Multiple improvements to the "View Mode" menu of the Viewport, including a feature request from JIRA UE-81469. Most of these improvements are related to the submenu of "View Mode" called "Buffer Visualization":
Issue 1/6 (the JIRA itself): The "View Mode" UI displays as its title the name on the selected category or subcategory chosen by the user (or otherwise the default one). However, this behavior was not consistent across different categories. For the "Buffer Visualization" category, if any of its subcategories were chosen, "View Mode" was only displaying "Buffer Visualization" as title, rather than the particular subcategory chosen. This was not the case for the other 2 categories ("Level of Detail" and "Optimization Viewmode").
Solution 1: The displayed name of "View Mode" is now forced to be the exact chosen (sub)category, regardless of the category ("Buffer Visualization", "Level of Detail", or "Optimization Viewmode").
Issue 2/6: The name displayed as the selected "View Mode" was being assigned in parallel with the displayed name of the buttons representing each (sub)category. This resulted in some categories and subcategories having different names in the buttons than in the "View Mode" label itself. The behavior was also not consistent across the different menus inside "View Mode".
Solution 2: The displayed name of the chosen label is forced to match the displayed name of the button itself.
Issue 3/6: "Optimization Viewmodes" was the only category without an icon.
Solution 3: Icon assigned to one of the icons of its subcategories. In particular, the one from "Quad Overdraw".
Issue 4/6: "Buffer visualization" was the only category without a proper tooltip, it was displaying a FName, rather than a more human-readable FText.
Solution 4: Assigned its tooltip to the FText field of DisplayedName.
Issue 5/6: When the subcategory "Overview" (of "Buffer Visualization") was chosen, the displayed name on each individual subwindow that are generated corresponded with limited FNames (rathern than a more human-readable text).
Solution 5: Assigned their value to the FTexts corresponding to their DisplayedName value.
Issue 6/6: Inside the possible Buffer Visualization Materials, `LightingModel` and `ShadingModel` are being used interchangeably all over the code, leading to missmatches and confusion for the user. E.g., `UMaterialInterface` and `UMaterial` use `LightingModel`, while `FBufferVisualizationData` (thus `FBufferVisualizationMenuCommands` and `FEditorViewportClient`) use `ShadingModel`.
Solution 6: Assigned all of the above classes to the same value.
Issue and solution 7 added in previous CL # 10228324.
#rb chris.gagnon
[CL 10286305 by Gines Hidalgo in Dev-Editor branch]
New feature: Added the capability of adding Radio buttons to the submenu main button (not only to its entries).
This CL is the first of 2 CLs that introduce multiple improvements on the "View Mode" menu of the Viewport, including a new feature request from JIRA UE-81469. However, we isolate this particular new feature into an isolated CL given that it can be applicable anywhere in the Editor, not only for "View Mode".
Issue: If any subcategory of "View Mode" was chosen, the user could not know in which category it was located (unless the user manually looked into each category until he found the selected one).
Solution: Added the checked functionality (with a radio button) to each one of the categories, behaving similarly to any subcategory. This way, both the radio button of the category and the one from the specific subcategory will be checked simulatenously.
More technical details:
Adding this functionality to "View Mode" means adding the functionality of "FUIAction::FIsActionChecked" into "AddSubMenu", which includes modifications to "MultiBox", "SMenuEntryBlock", and "MultiBoxBuilder".
1) We are changing a submenu so it has a radioButton
2) To specify a radio button a developer has to use a different API that includes a delegate (FUIAction) to say if it should be checked or not before this CL
3) The different API for AddSubMenu was not passing along the command list for that child submenu to use
4) The updated code now passes the command list along for the child submenu to use
#rb rex.hill
[CL 10228324 by Gines Hidalgo in Dev-Editor branch]
#jira none
#rb dave.belanger
#rn UMG Editor: The Replace with context menu in the Hierarchy view now support to replace a widget with the content of one of it's Named Slot.
[CL 10128123 by Vincent Gauthier in Dev-Editor branch]
Bug fix: Close Asset Editors warning while loading layout had 2 identical options: No and Cancel. Removed the Cancel option to avoid the duplicated option.
#rb none
[CL 10125714 by Gines Hidalgo in Dev-Editor branch]
Some displayed error messages about paths being too long are more informatives and include full path and current/maximum length allowed.
#rb none
[CL 10119068 by Gines Hidalgo in Dev-Editor branch]
Solved mini-bug when saving a layout with path too long: It was wrongly checking the relative path length rather than the fulll one.
#rb none
#fyi laura.klinefelter
[CL 10119067 by Gines Hidalgo in Dev-Editor branch]
