Refactored FindField into FindUField and FindFProperty to avoid confusion caused by the fact that FindField<UField> will no longer return FProperties.
#jira UE-90683
#rb Steve.Robb
#tests Basic editor functionality test, cooked and ran PC client and server, bot soak tests for two hours
#ROBOMERGE-OWNER: robert.manuszewski
#ROBOMERGE-AUTHOR: robert.manuszewski
#ROBOMERGE-SOURCE: CL 12190998 in //UE4/Release-4.25/... via CL 12190999
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v661-12148976)
[CL 12191300 by robert manuszewski in Main branch]
#rb chris.gagnon
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 11604269 via CL 11604360 via CL 11604439
#ROBOMERGE-BOT: (v656-11643781)
[CL 11743509 by rex hill in Main branch]
#ROBOMERGE-SOURCE: CL 11567023 via CL 11567108 via CL 11567120 via CL 11567133
#ROBOMERGE-BOT: (v654-11333218)
[CL 11567144 by rex hill in Main branch]
In a project with a lot of assets (let's say ~400K assets), SAssetView::ProcessRecentlyAddedAssets() would process a single asset during it's alloted time slice. The recreation of the set on each call would make the editor run at >10fps until the whole array is processed, at one asset per tick.
It's easy to reproduce by starting the editor and clicking on the "Content" root in the Content Browser, then typing anything in the Filter box while the asset discovery is in progress. The asset discovery will complete but the editor performance will be degraded until the filter is cleared.
With these changes, all new assets are processed in the allowed time with a single call to ProcessRecentlyAddedAssets()
#rb jamie.dale
#ROBOMERGE-SOURCE: CL 11292517 via CL 11292526 via CL 11292528 via CL 11292529
#ROBOMERGE-BOT: (v647-11244347)
[CL 11293016 by sebastien lussier in Main branch]
#jira
#rb Lauren.Barnes
#rnx
#ROBOMERGE-SOURCE: CL 11258423 via CL 11258471 via CL 11258485
#ROBOMERGE-BOT: (v647-11244347)
[CL 11258916 by jamie dale 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]
When docked, the collections view appears in a splitter below the paths view and is disconnected from the omni-search
#jira
#rb Lauren.Barnes
#ROBOMERGE-SOURCE: CL 10655445 via CL 10655505
#ROBOMERGE-BOT: (v609-10634694)
[CL 10655521 by jamie dale in Main branch]
This is accomplished by filtering out the recursive classes list to only the intersection between the supported asset classes and the backend filter's classes list if one is set. FARFilter::Append() creates the union of these lists, which would cause an excessive amount of classes to be displayed.
#rb chris.gagnon
#ROBOMERGE-SOURCE: CL 10319971 via CL 10320038
#ROBOMERGE-BOT: (v593-10286020)
[CL 10320040 by sebastian nordgren in Main branch]
#rb chris.gagnon
#rnx
#ROBOMERGE-OWNER: marc.audy
#ROBOMERGE-AUTHOR: sebastian.nordgren
#ROBOMERGE-SOURCE: CL 10069511 via CL 10069512
#ROBOMERGE-BOT: (v574-10069753)
#codereview Sebastian.Nordgren
[CL 10074271 by marc audy in Main branch]
Replicated from CL# 7924370.
#rb none
#ROBOMERGE-OWNER: steve.robb
#ROBOMERGE-AUTHOR: steve.robb
#ROBOMERGE-SOURCE: CL 9279060 via CL 9279063
#ROBOMERGE-BOT: (v443-9013191)
[CL 9279836 by steve robb in Main branch]
#jira UE-77252
#rb lauren.ridge
[FYI] jamie.dale
#ROBOMERGE-SOURCE: CL 7327659 via CL 7351608
#ROBOMERGE-BOT: (v371-7306989)
[CL 7397739 by rex hill in Main branch]
(Support was added to anything that uses AssetUtil::ExtractAssetDataFromDrag)
[FYI] robert.osborne
#rb matt.kuhlenschmidt, jamie.dale
#ROBOMERGE-SOURCE: CL 5762914 via CL 5763787
[CL 5763822 by patrick enfedaque in Main branch]