Compatible UIToggle mapping with AvailableChoices

Lafiel · Mar '21

This is a serious problem, hence, I insist on this here.
In the past, UIToggle modes were simply addressed by their ordered numbering starting from 0 to N.
With this change it's possible to customize for different option modes. However, as is there is no translation mapping happening with the AvailableChoices onto pre-existing/default modes (from 0 to N). This messes existing implementations settings as well as every time there is a new change with the UIButton. It's put a huge burden on updating and when UIButton changes are made.
If a mapping would happen not only would it be possible to hand over out-of-order options shuffling (more design freedom) but would reduce updating to a mere renaming of the UIToggle at most or not at all even.

The code could look just like:

			Default = 0
			AvailableChoices = [203,105,350,11]
			MappedChoices = [-1,0,1,2]
			ToggledOnChoices = [1,2]

Walt · Mar '21

You know you can set Mode = X, right?

Lafiel · Mar '21

Walt That is the problem. I don't want to because

there are a lot of buttons and parts
when you have to expand the button you have to go all over the parts and change the settings. With complex logic in parts this can be messy and error prone. It's a maintenance nightmare for no reason.
It makes it incompatible when changing out UIbuttons because the numbering could be totally different.

Walt · Mar '21

Lafiel when you have to expand the button you have to go all over the parts and change the settings

I don't understand why you have to do this.

Lafiel It makes it incompatible when changing out UIbuttons because the numbering could be totally different.

So make the numbering the same?

Lafiel · Mar '21

Walt

For example expanding on resources or on function features not possible before and their order
Because currently you can't shuffle so numbering the same is not possible or will only mess it up more.