android-design-library

问题 I'm trying to use TextInputLayout in my XML, and I'm meeting this error : java.lang.RuntimeException: Unable to start activity ComponentInfo{fr.jechange.moncompte/fr.jechange.moncompte.SignUpActivity}: android.view.InflateException: Binary XML file line #36: Error inflating class android.support.design.widget.TextInputLayout [...] Caused by: android.view.InflateException: Binary XML file line #36: Error inflating class android.support.design.widget.TextInputLayout [...] Caused by: java.lang

问题 Adding enterAlways to the scroll flags of the Cheesesquare demo: <android.support.design.widget.CollapsingToolbarLayout android:id="@+id/collapsing_toolbar" android:layout_width="match_parent" android:layout_height="match_parent" android:fitsSystemWindows="true" app:contentScrim="?attr/colorPrimary" app:layout_scrollFlags="scroll|exitUntilCollapsed|enterAlways"> results in a wrong layout: During scrolling down, the header comes in correctly but it doesn't stop in the correct position.

问题 I'm trying to show a DialogFragment full-screen such that the ActionBar is still visible but the tabs in a TabLayout are hidden. The image on the left is what I've managed to achieve; the image on the right is what I'm aiming for: There are two issues: The tabs are still shown, which the user can interact with; Because of the extra FrameLayout to show the dialog, the ViewPager content is still visible (the FAB button is not part of the dialog). This also means that the user can interact with

问题 I am developing an android application,In that I am using a Layout that contains a root layout(invitation_single) and nested layout(hidden). When I am on click root layout the nested layout display along with root layout that works fine. now my output is display like below image but i am expecting my output as, that means if am click "event2" then simultaneously nested layout(yes,no,maybe buttons) of first "event" needs to hide,but if i have a single event then the nested layout of that event

问题 In my app, I'm displaying a Toolbar with the home button visible. In some screens this works as an up button, in others not. That works fine. Problem is that when importing the design support library, the home button is not shown in the toolbar. This happens just by importing it, not a single line of code changed. I'm importing it in Gradle with: compile 'com.android.support:design:22.2.0' Do I need to change something in code for the design library not to make the home button disappear? Is

问题 Like in chat applications whenever we want to send messages soft keypad pop ups which also auto scroll the last seen messages to top of the soft keypad provided that nothing is hidden behind the soft keypad. But in my case the keypad hides the conversations. How to fix this issue and I have used to recycler view for displaying the messages. I used android.support.v7.widget.RecyclerView 回答1: With RecyclerView you can achieve this as follows: LinearLayoutManager linearLayoutManager = new

问题 OK, the behavior or my NavigationView works. I click on the settings and it takes me there. I click on my first item, it does what it should. I click on the second item, it does what it should. However, my issue is with the selection state. I will click on an item, and it will not select it. The only selection that works is my Settings menu. When I click on that item, the settings menu will become selected, along with all previous items I clicked on. Scenarios On App Load Go to NavigationView

问题 I have a vertical linear layout with some input fields. Using TextInputLayout I get a nice flow with labels and built-in error messages. My problem is when I add and remove the error-messages. If I add an error message it is positioned below the edit-text and everything looks good. If I remove the error message with setError(null) the message is removed but the space is still there. This is per googles design apparently(see https://code.google.com/p/android/issues/detail?id=176005). I would

问题 I'm new here, so bear with me! I'm sorta confused about the new Design Support Library (and how one implements support libraries), and I had a two questions: I'm confused about how support libraries are implemented. Is it something as simple as saying 'if the OS version is below version 5.0, use the V7 support library', or would I have to code an 'Alternative Layout'(One for devices running +5.0, and one for devices running older version of android?) Does the Design Support Library replace or

问题 When using a WebView inside a NestedScrollView there are a few issues. The main one I'm fighting is that sites which load more content as you scroll down don't work well, for example vimeo.com. Also setting the view to LAYER_TYPE_HARDWARE doesn't work, probably for the same reason, it basically crashes because of the height. So, is there an alternative to the NestedScrollView if I want to use CoordinatorLayout in order to collapse the toolbar when the user scrolls inside the WebView ? My code