For now did not deprecate usage of AddMenuSeparator in menu builders due to the extreme number of fiiles this touches
[CODEREVIEW] rex.hill
#ROBOMERGE-SOURCE: CL 12669820 via CL 12669822 via CL 12669823
#ROBOMERGE-BOT: RELEASE (Release-Engine-Staging -> Main) (v675-12543919)
[CL 12671630 by matt kuhlenschmidt in Main branch]
#rnx
#jira
#ROBOMERGE-SOURCE: CL 12403198 via CL 12403230 via CL 12404729
#ROBOMERGE-BOT: (v671-12333473)
[CL 12405063 by rex hill in Release-Engine-Staging branch]
#rnx
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 12402687 via CL 12402690 via CL 12404501
#ROBOMERGE-BOT: (v671-12333473)
[CL 12404533 by rex hill in Release-Engine-Staging branch]
#rnx
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 12382023 via CL 12382025 via CL 12390417
#ROBOMERGE-BOT: (v671-12333473)
[CL 12392050 by rex hill in Release-Engine-Staging branch]
#jira
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 12247311 via CL 12247549 via CL 12247768
#ROBOMERGE-BOT: (v668-12245121)
[CL 12247793 by rex hill in Main branch]
Now there is a separate api on editor viewports to set and remove a temporary override state. Deprecated existing methods and fixed up use cases.
#ROBOMERGE-OWNER: matt.kuhlenschmidt
#ROBOMERGE-AUTHOR: matt.kuhlenschmidt
#ROBOMERGE-SOURCE: CL 11498109 via CL 11498156 via CL 11498165
#ROBOMERGE-BOT: (v654-11333218)
#rb none
[CL 11498464 by matt kuhlenschmidt in Main branch]
#rnx
#rb none
#ROBOMERGE-SOURCE: CL 10869241 via CL 10869527 via CL 10869904
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870586 by ryan durand in Main 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]
We've had several cases where the previously default alphabetical sorting caused performance issues when it wasn't needed. We now require you to explicitly choose either slow alphabetical sorting or fast non-alphabetical order.
The fast order does not decode, access or compare actual string data, but the order is not stable between process runs.
#rb steve.robb
[CL 5915265 by Johan Torp in Dev-Core branch]