- It is now possible to define payload parameters for events again
- Creating a new event endpoint will leverage custom event nodes rather than separate functions. This is now possible due to the added flexibility that generated function graphs gives us.
- Users can now also specify which pin to pass the bound object through (if any) - previous rules apply (only object and interface pins supported)
- Reworked quick-binding menu to use the blueprint graph action menu
#rb Max.Chen, Matt.Hoffman
[CL 9069042 by Andrew Rodham in Dev-Editor branch]
- Uses a sparse object annotation to ensure minimal overhead for any K2Node instance that does not have this bound
#rb Dan.OConner
[CL 9068581 by Andrew Rodham in Dev-Editor branch]
Generated function graphs can be created as part of the compilation process and are ephemeral (only lasting the duration of the compile), but will still be used to generate bytecode and UFunctions on the final class layout. External clients can hook into this process by binding to UBlueprint::GenerateFunctionGraphsEvent and spawning the necessary intermediate graphs on the compiler context using FKismetCompiler::SpawnIntermediateFunctionGraph. GenerateFunctionGraphsEvent is a dynamic delegate, meaning that all bindings will be serialized into the package, enabling composition workflows within a single package.
Generated function graphs are also visible as an intermediate build product with this Blueprint developer setting enabled.
#rb Dan.OConner
[CL 9068567 by Andrew Rodham in Dev-Editor branch]
- Add minimum window size
- Update icon in menu
- Add reset all customizations button with prompt
#rb none
#rnx
[CL 9054774 by Rex Hill in Dev-Editor branch]
