Radio is saving values, while Select - not

The CMS Questions
1

https://take.ms/xIsOP short screencast to show

blueprint:
    type: builder
    fieldsets:
      setlists:
        label: Sarašas
        fields:
          widthdesktop:
            label: Stulpeliai
            type: radio
            options:
              12: 1
              6: 2
              4: 3
              3: 4
              2: 6
            width: 1/6
2

Maybe it’s because human values can’t be numbers with Select? Tried to change and it works this way:

blueprint:
    type: builder
    fieldsets:
      setlists:
        label: Sarašas
        fields:
          widthdesktop:
            label: Stulpeliai
            type: select
            options:
              12: one
              6: two
              4: three
              3: four
              2: six

Still would be nice to use both words and numbers.

3
4

In this case just for less space in interface would be better to use Select.

5

Ah, ok, I see what you mean. Changed to this and it works:

      12: '1'
      6: '2'
6

Less space doesn’t mean better user experience.

7

Yes, depends on case, I usually use radios if there are few values, as then there is no need to open list, but in this case want to have one line of fields for settings. Anyway, problem is solved, thanks.

Made by this example to store different values, than editor sees, and works perfect:

fields:
  category:
    label: Category
    type: select
    options:
      - value: '100'
        text: Design
      - value: '200'
        text: Architecture
8

Tried another solution to change human value: 12 / $data->widthdesktop(), but works very strange: $data->widthdesktop() returns “1” all the times, not depending what real value is selected.