UIToggleProxy for BlueprintSprite

Lafiel

When using the new AvailableChoices feature for selective option of the option range of an UI button within ToggledComponents then it's not accessible to BlueprintSprite.
So I'm suggesting having a proxy to allow access.
Or better yet combine it with a previous request for making BlueprintSprite toggle-able or available within ToggledComponents.

Walt

I'm a little confused, is the problem simply that choices not listed in AvailableChoices can be selected in build mode? If so, I can probably fix that.

Lafiel

Walt No. The problem is with ShowOnlyInToggleMode and ToggleID.

Walt

Lafiel Then I don't understand what the problem is.

Lafiel

Walt This doesn't work.

ModeAComponents
{
	Type = ToggledComponents
	Toggle = ModeA
	Components
	{
		UI
		{
			Type = UIToggle
			ToggleID = "My_UI"
			Default = 0
			AvailableChoices = [-1, 0, 1]
			ToggledOnChoices = [0, 1]
		}
	}
}
ModeBComponents
{
	Type = ToggledComponents
	Toggle = ModeB
	Components
	{
		UI
		{
			Type = UIToggle
			ToggleID = "My_UI"
			Default = 1
			AvailableChoices = [1, 2]
			ToggledOnChoices = [1, 2]
		}
	}
}
Blueprints0
{
	Type = BlueprintSprite
	ShowOnlyInToggleMode
	{
		ToggleID = "My_UI"
		Mode = 0
	}
}
Blueprints1
{
	Type = BlueprintSprite
	ShowOnlyInToggleMode
	{
		ToggleID = "My_UI"
		Mode = 1
	}
}

Walt

Lafiel What does that have to do with AvailableChoices?

Lafiel

Walt Because of the use of the ID, buttons cannot be re-used concurrently within a part which requires them to be duplicated using different IDs. But duplication requires blueprints to be also duplicated. For the same reason the use of ToggleComponent fails because the ID would not exist.