Behavior noticed when adding RadioButton and initial check at the same time in code

I was addicted to RadioGroup and RadioButton

This is the first post.

I noticed it while working at Kotlin, so I output it appropriately.

Premise

• RadioGroup is defined in XML
• AddView RadioButton there on the code side
• A shape that is used quite often

Behavior you want

"* I want to add the initial value of the Radio Button that will be added *"

Often.

code

list = listOf(1, 2, 3)//Meaningful information
radioGroup = findById(R.id.radio_group) as RadioGroup
for (data in list){
    val radioButton = RadioButton(this)
    if (data == 1){
        //I want to use it as an initial value!
        radioButton.isChecked = true
    }
    radioGroup.addView(radioButton)
}

Looks good

The purpose I saw is checked and very good

checkedRadioButtonId cannot be taken correctly

• Hamari point here
• checkedRadioButtonId wants to use but it doesn't work
• Maybe I can't see if addSubView is checked later ...?

Refact

list = listOf(1, 2, 3)//Meaningful information
radioGroup = findById(R.id.radio_group) as RadioGroup
for (data in list){
    val radioButton = RadioButton(this)
    //Register RadioButton as SubView immediately after declaration
    radioGroup.addView(radioButton)
    if (data == 1){
        //I want to use it as an initial value!
        radioButton.isChecked = true
    }
}

moved

I did it.

Impressions

• It's not final, but did you see the parameters inside when you addedSubView?
• When multiple items are added, if you check all of them, can you make all checked items?
• Not practical, none have been checked
• I realized that addSubView is not just a copy layout, but a reference layout (?).
• In this case, it seems safer to play with View with addSubView first ... Isn't it?
• As explained in Kotlin, it seems that Android Java will probably behave in the same way.