android-databinding

问题 I am developing an app that has tab layout as the image. I’d like to use MVVM architecture with data binding library but I am new with this framework. I can do this without using MVVM by normally setup tab layout using ViewPager as this sample. Normal tab layout without MVVM and data binding: activity_main.xml: <android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" android:layout_width=

问题 I'm trying to use androids databinding feature in new project and so far very happy with it. But now i came across a problem in my recyclerviews viewholder. My viewholder uses different layouts (based on the viewtype when it gets created) public MediaViewHolder onCreateViewHolder(ViewGroup parent, int viewType) { switch(viewType){ case HEADER: int layout = R.layout.item_media_header; break; case DEFAULT: int layout = R.layout.item_media_default; break; case SMALL: int layout = R.layout.item

问题 I have a data binding layout that contains a frame layout with <include> of other layout inside: <FrameLayout android:id="@+id/global_actions_frame_layout" android:layout_width="match_parent" android:layout_height="0dp" android:layout_weight="0.075" android:background="@color/colorToolBar"> <include android:id="@+id/included" layout="@layout/global_actions"> </include> </FrameLayout> the layout has image buttons inside in this format: <ImageButton android:id="@+id/settingsButton" android

问题 I am implementing DataBinding , it is working perfect, but it is not allowing me to use jackOptions . It throws error Data Binding does not support Jack builds yet while build. Here is my build.gradle android { defaultConfig { ... dataBinding { enabled true } jackOptions { enabled true } } compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 } } 回答1: From yigit's comment it's clear that this functionality is still under development as he and

问题 In Yigit Boyar and George Mount's talk on Android Databinding they illustrate how easy it is to bind to TextWatcher 's onTextChanged (at 13:41). On a Button. Are their slides wrong? First of all the Button View doesn't have an onTextChanged property. It neither has a setOnTextChanged method. Neither does EditText . But they both have addTextChangedListener which takes a TextWatcher as input. So what are they talking about? How do they do it? Their example code does not compile, but gives this

问题 I am using Data Binding in my project, when using <layout> and <data> in my xml binding class is not generated. For example i have activity_main.xml <?xml version="1.0" encoding="utf-8"?> <layout xmlns:android="http://schemas.android.com/apk/res/android"> <data> </data> <RelativeLayout android:layout_width="match_parent" android:layout_height="match_parent"> </RelativeLayout> </layout> Now if i am writing ActivityMainBinding in my activity/fragment it shows error that class is not available.

问题 I'm using android data binding and it is working fine whenever I'm not using the include tag. If I included a view using the tag (even it is displaying on the app) but the data binding object doesn't recognize the views of the included layout. These are my layout files. internet_unavailable.xml <?xml version="1.0" encoding="utf-8"?> <layout xmlns:android="http://schemas.android.com/apk/res/android"> <LinearLayout android:layout_width="match_parent" android:layout_height="wrap_content" android

问题 I'm trying to set the visibility and the src of an ImageView using data binding. I don't know why this error is showing up, and I truely believe that this was working at one point, but I could be wrong. Layout: <data> <import type="android.view.View" /> <import type="android.support.v4.content.ContextCompat" /> <variable name="viewData" type="com.myapp.SomethingViewData" /> </data> ... <ImageView ... android:src="@{ContextCompat.getDrawable(context, viewData.getIconResource())}" android

问题 I have a ParentFragment and a ChildFragment . They are working pretty fine. My problem is that in the future I might create many child fragments and this makes me write this boilerplate code for every single child fragment. Thus, I would like to optimize my ParentFragment so that I do not have to write boilerplate code for every single new child framment I create in the future. ParentFragment abstract class ParentFragment<T: ViewDataBinding>: Fragment() { @LayoutRes abstract fun

问题 When I'm adding the androidTestCompile 'com.android.support.test.espresso:espresso-contrib:2.2.1' in the gradle and run an Espresso test, I get the following error: Testing started at 5:59 PM ... 02/08 17:59:58: Launching changeText_sameAct...() No apk changes detected since last installation, skipping installation of /Users/xxx/Documents/home/MasterDetails/app/build/outputs/apk/app-debug.apk $ adb shell am force-stop databinding.com.masterdetails No apk changes detected since last