#jira UE-16861 - material node search is failing to find lots of things
Changed to using range-based loops so the array name is only referenced by the loop itself, to guard against future problems of this sort.
#codereview Michael.Schoell
[CL 2607606 by Richard TalbotWatkin in Main branch]
#jira UE-17964 - Rotating brushes in two axis, then rotating UVs cause materials to stretch on BSPs
Fixed UEditorEngine::polyUpdateMaster so that the inverse rotation transform is performed with FMatrix::InverseTransformVector, instead of erroneously using a negated rotator.
[CL 2607404 by Richard TalbotWatkin in Main branch]
#UE4 Lowered verbosity on nullrhi warning in automated tests as this is an expected case under normal circumstances.
--------
Integrated using branch Ue4-To-UE4-Fortnite-Simple (reversed) of change#2606958 by Bob.Tellez on 2015/06/30 22:22:04.
[CL 2606959 by Bob Tellez in Main branch]
#UE4 Now describing in more detail why a blueprint issue should be fixed in ShouldBeFixed().
--------
Integrated using branch Ue4-To-UE4-Fortnite-Simple (reversed) of change#2606271 by Bob.Tellez on 2015/06/30 15:18:57.
[CL 2606273 by Bob Tellez in Main branch]
change summary:
- added a new "InternalUseParam" UFUNCTION() meta to support tagging function parameters as internal use only (=> hidden | not connectable)
- added a UK2Node_CallFunction::IsConnectionDisallowed() override method; returns 'true' if the 'bNotConnectable' flag is set on the node's pin (and will emit a compile error in existing projects if something is connected to it)
- modified FBlueprintEditorUtils::GetHiddenPinsForFunction() to accept an optional 'InternalPins' TSet as an output; on return, this will contain the subset of hidden pins that are marked as "InternalUseParam"
- modified UK2Node_CallFunction::CreatePinsForFunctionCall() to set the 'bNotConnectable' pin attribute to 'true' if "InternalUseParam == '<PinName>'" is included within the UFunction metadata
- modified the AActor::AddComponent UFUNCTION() decl to switch the "HidePin" meta to "InternalUseParam" for the 'ComponentTemplateContext' parameter (because it should not be connectable)
- modified UK2Node_CallFunction::NotifyPinConnectionListChanged() to refresh the node to hide pins corresponding to internal-only params once the (invalid) connection in an existing project has been broken
#codereview Mike.Beach
[CL 2606203 by Phillip Kavan in Main branch]
Selection set will not be added to the transaction buffer if it contains any PIE objects
Transaction will not actually be created when clicking on a PIE object in the scene outliner
#codereview Matt.Kuhlenschmidt, Richard.TalbotWatkin
[CL 2606122 by Marc Audy in Main branch]
#jira UE-17417 - User must run FixUp Redirector two times to complete operation
Added referencing assets' paths into the list in FAssetFixUpRedirectors::UpdateAssetReferencers so that the asset references lists are updated correctly.
Also fixed a problem leading to duplicate entries in the PendingDeletes list in FAssetDeleteModel.
[CL 2605630 by Richard TalbotWatkin in Main branch]
The issue here is that the derived destructor for FFeedbackContextEditor would destroy it's TWeakPtr<SWindow>, proceeded by the destruction of any remaining FScopedSlowTasks held in the LegacyAPIScopes array. This destruction may have caused FFeedbackContextEditor::FinalizeSlowTask to be called which could have resulted in the TWeakPtr being used after its RefereceCount was deleted, causing a memory overwrite. I can't see any code in the wild which could have caused this, but I've also added some additional safety checks to catch error conditions earlier.
[CL 2605382 by Andrew Rodham in Main branch]
- Do not cache off the world in the actor binding manager
- Ensure tracks are fully updated when a map changes
- Properly clean up spawnable actors when a world is torn down
[CL 2604571 by Matt Kuhlenschmidt in Main branch]
UE-17445 - Data Table Enums Fail to import correctly
The Data Table editor UI will now show you the friendly name of the enums in its grid panel (matching what the property panel shows).
The Data Table import will now fallback to trying to import using a friendly name if no matching enum entry was found for the given name. This avoids the need to use the standard User Defined Enum names of "NewEnumeration0", "NewEnumeration1", etc, but does make the CSV/JSON data less robust against renaming the enum entries. CSV/JSON exporting will still use the internal names.
[CL 2604128 by Jamie Dale in Main branch]