IssueTracker

Fix is checked in, but probably won't be out until the release after the upcoming one.

starting in 3.0 the top level directory will be "cmdline-tools"

3.0 is out in the beta channel. You'll see it if you specify --channel=1 on the sdkmanager commandline.
I guess we don't have release notes right now, beyond looking at the fixed bugs :-/

Hi,

I'm kind of short on time for the next few days and won't get time to make a small project till after the weekend.
If I just send you (or github invite you ) the project will it stay within Google?

Also I think I've narrowed down the cause.


I have multiple BindingAdapters annotated with @BindingAdapter("app:text").

One for each of the number types.
//-------------------------------------------------------------------------------------------------//

@BindingAdapter("app:text")
fun setDoubleInTextView(tv: TextView, dbl: Double?) {

    try {
        //This will occur when view is first created or when the leading zero is omitted
        if (dbl == null && (tv.text.toString() == "" || tv.text.toString() == ".")) return

        //Check to see what's already there
        val tvDbl = tv.text.toString().toDouble()

        //If it's the same as what we've just entered then return
        // This is when then the double was typed rather than binded
        if (tvDbl == dbl)
            return

        //If it's a new number then set it in the tv
        tv.text = dbl?.toString()

    } catch (nfe: java.lang.NumberFormatException) {

        //This is usually caused when tv.text is blank and we've entered the first digit
        tv.text = dbl?.toString() ?: ""

    }//catch

}//setDoubleInTextView

//- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -//

@InverseBindingAdapter(attribute = "app:text")
fun getDoubleFromTextView(editText: TextView): Double? {

    return try {
        editText.text.toString().toDouble()
    } catch (e: NumberFormatException) {
        null
    }//catch

}//getDoubleFromTextView

//-------------------------------------------------------------------------------------------------//

@BindingAdapter("app:text")
fun setNullableIntegerInTextView(editText: TextView, int: Int?) {

    val intStr = int?.toString()

    intStr?.let {
        if (intStr != editText.text.toString())
            editText.text = int.toString()
        return
    }//let

    if (editText.text != null && editText.text.toString() != "")
        editText.text = null
}//setIntegerInTextView

//- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -//

@InverseBindingAdapter(attribute = "app:text")
fun getNullableIntegerFromTextView(editText: TextView): Int? {

    return try {
        editText.text.toString().toInt()
    } catch (e: NumberFormatException) {
        null
    }//catch

}//getIntegerFromTextView

//-------------------------------------------------------------------------------------------------//

@BindingAdapter("app:text")
fun setIntegerInTextView(editText: TextView, int: Int) {

    val intStr = int.toString()

    intStr.let {
        if (intStr != editText.text.toString())
            editText.text = int.toString()
        return
    }//let
}//setIntegerInTextView

//- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -//

@InverseBindingAdapter(attribute = "app:text")
fun getIntegerFromTextView(editText: TextView): Int {

    return try {
        editText.text.toString().toInt()
    } catch (e: NumberFormatException) {
        0
    }//catch

}//getIntegerFromTextView

//-------------------------------------------------------------------------------------------------//


My thinking was (and it seemed to work in version 3.5) that the compiler would figure out what overloaded method I was actually referring to based on the variable type.
It does seem to get it right at runtime.
However if I create another Int type BindingAdapter:

@BindingAdapter("app:textInputEditText")
fun setIntegerInTextInputEditText(editText:  TextView, int: Int) {

    val intStr = int.toString()

    intStr.let {
        if (intStr != editText.text.toString())
            editText.text = int.toString()
        return
    }//let

}//setIntegerInTextInputEditText


and then in my layout I do this:
 app:textInputEditText="@={viewModel.tempProductQty}"  
instead of
 app:text="@={viewModel.tempProductQty}"  

I don't get any squiggly red lines.

Maybe this is the right way and I had been previously "breaking the rules".

Let me know what you think.

You can give me a quick call if you want to chat about it.

Shane

It turns out to be an issue specific for Kotlin and the fixed should be released by 4.1 Canary 9.
Also, if you see similar unwanted "Cannot find a getter" error for custom xml attribute, you can try ctrl/command + B to search the declaration of the xml attribute and check if you can find all declarations for getters and setters.

Cool, Glad to help.