[=;188956]
Is there any reason for change? Because it is a pretty bad change.
We already had problem with C++ variables, and BP change only makes things worse rather than fixing it.
Consider case for example, which has been happening to us on multiple large productions:
https://dl.dropboxusercontent.com/u/2300830/e4rt43etg.jpg
is a BP placed in a level. Everything except for the green marked properties should not be visible, but it is, because all those properties came in from the C++ base class. The green properties internally control everything, so the end user is only expected to change those green properties. They are faced however with a long list of very confusing properties, most of which they cannot change or it will break things/not work.
We have had it happen before that people start editing stuff they are not suppose to, because it is not clear what they should and should not change. And that was a problem already with C++ based classes, but now that BP enforces you to do the same thing problem just got worse.
Speaking of which, what we also don’t have is the ability to make grayed out properties in BP, and information boxes. I want to be able to display info (text/values) in the properties to the end user. For example if I have a text field, I want to be able to display somewhere “text field length is currently 65 characters” to ensure there is feedback to the end user as to how he is doing char limit wise (or for whatever other reason).
[/]
Seconded. Just because I want something to be accessible from other blueprints doesn’t mean I want it to be accessible to the level designer or cluttering up my actor properties. Why’d someone think was a good idea?