Problem is @dimen/place_holder_size, it returns float while you are catching it as int change you BindingAdapter method to this @BindingAdapter({“bind:url”, “bind:size”}) public static void loadImage(ImageView imageView, String url, float size) { } you can refer this
The correct syntax for calling a data-bind statement looks like “@{<some expression>}”, and so a ternary conditional would be “@{bool ? ifTrue : ifFalse}” Where those two values would be the (unquoted) values of what you would normally place into the XML without data binding. For example android:color=”@{isValid ? @color/green : @color/red}” Or, you can … Read more
Well, six months later but maybe i can help someone. You can do this simple trick: android:text=”@={“ + mObject.someNumber}” OBS.: You need at least Android Studio 2.3
1 Line Solution android:selectedItemPosition=”@={item.selectedItemPosition}” That’s it! No need to make custom BindingAdapter. Spinner already supports two-way binding by attributes selection and selectedItemPosition. See Android Documentation You just need to use two way binding selectedItemPosition so that change on spinner reflect on your model field. Example Item.class public class Item extends BaseObservable { private int selectedItemPosition; … Read more
EDIT 04.05.16: Android Data binding now supports two way-binding automatically! Simply replace: android:text=”@{viewModel.address}” with: android:text=”@={viewModel.address}” in an EditText for instance and you get two-way binding. Make sure you update to the latest version of Android Studio/gradle/build-tools to enable this. (PREVIOUS ANSWER): I tried Bhavdip Pathar’s solution, but this failed to update other views I had … Read more
The answer to your question is what is your goal? If you want to use MVVM for separation of concerns so that you can unit test your Viewmodel then you should try to keep everything that requires a Context separate from your Viewmodel. The Viewmodel contains the core business logic of your app and should … Read more
I seems the int you are providing is interpreted as a hex color, even though it seem intuitive that this setter should be expecting a resource ID. use the Context reference generated for each bindable view, and use it to convert the resource ID to the color you are pointing to, as described in the … Read more
I had the same warning, in my case changing the variable declaration from Boolean type to boolean type solve the problem: From: <variable name=”readOnly” type=”Boolean” /> To: <variable name=”readOnly” type=”boolean” /> So, maybe you can try with: <variable name=”selectMap” type=”android.databinding.ObservableMap<Integer, boolean>” />
In case you might be experiencing this issue with LiveData, you might’ve forgotten to set lifecycle owner of your binding; binding.setLifecycleOwner(lifecycleOwner)
The data binding unfortunately is not supported for styles: https://code.google.com/p/android-developer-preview/issues/detail?id=2613