# Inline struct editing doesn't work in foliage settings

**URL:** <https://forums.unrealengine.com/t/inline-struct-editing-doesnt-work-in-foliage-settings/300468>\
**Category:** UI\
**Tags:** property, unreal-engine, bug-report, editor, UI, question\
**Created:** [December 3, 2014, 2:28pm UTC](https://forums.unrealengine.com/t/inline-struct-editing-doesnt-work-in-foliage-settings/300468 "2014-12-03T14:28:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leszek\_Godlewski\_Astronauts\_1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Leszek\_Godlewski\_Astronauts\_1](https://forums.unrealengine.com/u/Leszek_Godlewski_Astronauts_1)\
**Post date:** [December 3, 2014, 2:28pm UTC](https://forums.unrealengine.com/t/inline-struct-editing-doesnt-work-in-foliage-settings/300468/1 "2014-12-03T14:28:40Z")

</div>

I have a struct ( `USTRUCT()`) that I can edit just fine in pretty much any object, for instance in `UPrimitiveComponent`:

```
UPROPERTY(EditAnywhere, BlueprintReadOnly, AdvancedDisplay, Category = Lighting)
FLightingChannelContainer LightingChannels;

```

![22834-channels.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/b/5/6b530c40f5d641623cd19bdb1a502738d68c99ed.png)

However, adding the very same two lines to `UFoliageType` has a somewhat incomplete effect:

 ![22835-channels2.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/1/9/a19f33f3debce02c97d1665d679b5b4badda4c5d.png)

I.e. the struct cannot be expanded and edited inline. The only way to edit it is to make modifications on the same struct somewhere else and copy/paste it around. This is obviously a suboptimal workflow.

**EDIT:** Actually, we can just open the thing up in the Property Matrix and there the struct is fully accessible again, but it would be neat if this additional step could be avoided.

Any recommendations?

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b666e59e](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b666e59e](https://forums.unrealengine.com/u/anonymous_user_b666e59e)\
**Post date:** [December 8, 2014, 5:30pm UTC](https://forums.unrealengine.com/t/inline-struct-editing-doesnt-work-in-foliage-settings/300468/2 "2014-12-08T17:30:55Z")

</div>

Hi ,

Could you provide a little more information about this issue? What version of the Engine are you using (and are you using the Binary version, or did you build the Engine from source code)? Could you provide a few more details about how you are setting up the struct and trying to use it?

---

<div class="post-metadata">

**Author:** ![Leszek\_Godlewski\_Astronauts\_1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Leszek\_Godlewski\_Astronauts\_1](https://forums.unrealengine.com/u/Leszek_Godlewski_Astronauts_1)\
**Post date:** [December 11, 2014, 10:12am UTC](https://forums.unrealengine.com/t/inline-struct-editing-doesnt-work-in-foliage-settings/300468/3 "2014-12-11T10:12:22Z")

</div>

Apologies for not providing those up front. The version is 4.6, built from source, no custom changes to UI code whatsoever.

The struct is nothing fancy, just a bunch of booleans:

```
USTRUCT()
struct FLightingChannelContainer
{
	GENERATED_USTRUCT_BODY()

	UPROPERTY(EditAnywhere, BlueprintReadOnly, Category = LightingChannels, meta = (DisplayName = "Static"))
	uint32	Channel0 : 1;
	// ...
};

```

This struct is simply added to `UFoliageType` as per my original post.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_b666e59e](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_b666e59e](https://forums.unrealengine.com/u/anonymous_user_b666e59e)\
**Post date:** [December 17, 2014, 7:33pm UTC](https://forums.unrealengine.com/t/inline-struct-editing-doesnt-work-in-foliage-settings/300468/4 "2014-12-17T19:33:14Z")

</div>

Hi ,

Thank you for the additional information that you provided. I was able to reproduce the issue that you have described, and I have entered a ticket about the issue to have it investigated further (UE-6815).
