BP inherited component editable desp. "not editable" flag

anonymous_user_2709d010 · December 16, 2015, 4:20am

Make a blueprint for an actor
My Blueprint has following component hierarchy, but I doubt it matters:

Static Mesh

----Box Collision

Give box collision a size and position and mark it as “not editable when inherited”

Derive a blueprint from this
Open derived BP in editor. You will be able to edit size and position of Box Collision.
Save BP and compile.
Leave editor
Restart editor and load BP
It will be of size and position given in base BP.

This is irritating and cost me a while to figure out that I forgot to set that flag. It should be so that nothing can be edited in a derived class in a component that is marked as “not editable” or there should be a t least a warning, but I don’t see what this “crippled editing” should be good for in first place if it is not persistent.

anonymous_user_33800a51 · December 16, 2015, 3:31pm

Hi ,

I tried this in 4.10.1 using Blueprints created in editor, and setting Editable when Inherited to False on component ensures I cannot edit them in a child derived from that BP. This shouldn’t be an issue because you shouldn’t be able to edit it at all. Did you create original BP using code? If so, can you show me code you used to create parent?

anonymous_user_2709d010 · December 20, 2015, 2:52am

project is a C++ based one. I have a C++ baseclass for all items in game. There is not much in it, I include source file here. From that I have an Item_BP class derived which is actual baseclass for each item in game

link text

anonymous_user_2b03d27c · December 21, 2015, 7:47pm

Hey -

I created an Actor class and a blueprint based on class. After adding a box component to blueprint and setting Editable in Children option to false I created a second BP which was correctly set to not be editable. If you are able to reproduce this in a new project without any added content can you upload that project and send a download link for us to test issue directly?

anonymous_user_2b03d27c · December 28, 2015, 6:35pm

Hi ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.