Using PC_Enum instead of PC_Byte with CreatePin results in incorrect pin

This is a bug that can make it confusing for users (and internal devs) to make custom nodes related to enums. 

This is occuring because the PC_Enum type was added after the original PC_Byte but 

FNodeFactory::CreateK2PinWidget was never updated to return the correct pin type for it. 

It should return the same thing as using PC_Byte does, which is a nice dropdown of the enum types. 

A note from Michael N: ideally everything that's currently an enum with PC_Byte would move over to PC_Enum and remove the strange legacy of the Enum ptr on UByteProperty, but it is probably a non-trivial refactor

[Image Removed]

1. Find a UEnum to use as an example (any UENUM will work)
2. Using the CreatePin method inside of a node's AllocateDefaultPin function, do the following

// Image on the left uses:
CreatePin(EGPD_Input, UEdGraphSchema_K2::PC_Byte, StaticEnum<EInputPinEnum>(), EnumInputPinName);

// And the right uses
CreatePin(EGPD_Input, UEdGraphSchema_K2::PC_Enum, StaticEnum<EInputPinEnum>(), InputPinName);

Result: Two different pin types would be created

Expected: The result should be the same

I am not able to find world outliner how to enable it?

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

I'm testing a vehicle demo for html5..when I packaging and testing it on chromium it won't show the object but a side of the object. What should be the issue?

How can i modify the param name in EQS node

Lighting Turns Black in Play Mode

What properties of the progress bar can be used for drag and drop highlighting?

What property of the Slider is the image used when dragging?

Does the ue packaged solution configuration need to be the same as the vs solution configuration?

When I open UE4 4.24.3 it appears that. Does anyone know how to solve?

Bullet replication problem. The players sees each other but does not see the bullet