android-support-library

Appcompat-v7 conflict in android

北城以北 提交于 2019-12-11 10:12:58
问题 I ran into a nasty problem. In my project I have a library (.aar) file which is including an appcompat-v7 compatibility library. Now in my project I also have another appcompat-v7 under the dependency section of gradle.build (app) file.. The problem is when I run the Application it throws an exception saying UNEXPECTED TOP-LEVEL EXCEPTION:com.android.dex.DexException: Multiple dex files define Landroid/support/v7/appcompat/R$anim; Here is my application gradle.build (app) file relevant part

Download Android Support v4 Jar Revision 9 (!)

删除回忆录丶 提交于 2019-12-11 09:59:00
问题 Revision 10 is the newest Android Support Library, but its bugged, so I can't use it. Where can I download Revision 9? I need the .jar from Revision 9, because on Revision 10 the Notification on Android 3 and 3.1 are bugged. I "hacked" the Rev10 to work, but the ViewPagerIndicator don't like it and don't work (my project don't compile anymore) with this .jar. Now I search the rev9 jar. Thanks in advance! 回答1: For those who are searching, here is a download link to a fixed r10 and a r9 (I know

Home button not shown when using the design support library

会有一股神秘感。 提交于 2019-12-11 09:38:27
问题 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

How to use a sliding transition with Compatibility Library v4 Fragment Transactions

柔情痞子 提交于 2019-12-11 09:22:16
问题 All I want is to be able to use FragmentTransaction.replace(...) and have fragments slide into and out of place just like activities, using the default activity animation. By default the fragments simply appear and disappear. That is an acceptable default behavior. With FragmentTransaction.setTransition(...) I can get Fragments to fade with a slight zooming animation. That is pretty cool, but it looks nothing like what activities do. With FragmentTransaction.setCustomAnimation(...) a

Failed to resolve: com.android.support:support-v13:26 [duplicate]

痞子三分冷 提交于 2019-12-11 08:08:23
问题 This question already has answers here : Failed to resolve: com.android.support:appcompat-v7:26.0.0 (12 answers) Failed to resolve: com.android.support:cardview-v7:26.0.0 android (24 answers) Closed 2 years ago . Everything has been working and compiling fine until I've added a TabLayout to an .xml layout. After I added it, the project just refused to compile and either all of my .xml files stopped showing anything and all of my library imports say "cannot resolve symbol ...". I don't

What replaced appcompat-v7 in AndroidX

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-11 07:48:40
问题 After migrating a couple of my older projects over to AndroidX it as though three of my dependencies are deprecated: implementation 'com.android.support:appcompat-v7:28.0.0' implementation 'com.android.support:design:28.0.0' implementation 'com.android.support:cardview-v7:28.0.0' I haven't been able to find a replacement for these dependencies. Does AndroidX have an equivalent for these dependencies? 回答1: Use in the order: implementation 'androidx.appcompat:appcompat:1.0.2' implementation

onAnimationEnd() called twice

一个人想着一个人 提交于 2019-12-11 06:45:13
问题 After updating the build sdk 27 from 23 came across this issue of onAnimationEnd firing twice in the code below when called. onAnimationStart is called only once and onAnimationRepeat is not called as expected. Now in the app when the user presses the back button one time, they are taken two steps back. All the libraries in gradle are using 27.0.2 which is the latest. This code used to work fine in sdk 23. Our min target is 16. I'm using a work around by using a isAnimating flag but would

Why should I use ActionbarSherlock? [closed]

跟風遠走 提交于 2019-12-11 06:40:01
问题 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 6 years ago . I have seen tons of answers related to usage of ActionbarSherlock. Even that I use it for months I still don't have an answer why should I really used? What more it gives than the regular Android support library?

java.lang.NoSuchMethodError: No static method isCtrlPressed(Landroid/view/KeyEvent;)

你。 提交于 2019-12-11 06:29:28
问题 I received the following Stack Trace in Android Studio (v.2.2.3): E/InputEventSender: Exception dispatching finished signal. E/MessageQueue-JNI: Exception in MessageQueue callback: handleReceiveCallback E/MessageQueue-JNI: java.lang.NoSuchMethodError: No static method isCtrlPressed(Landroid/view/KeyEvent;)Z in class Landroid/support/v4/view/KeyEventCompat; or its super classes (declaration of 'android.support.v4.view.KeyEventCompat' appears in /data/app/com.app.name-2/base.apk) at android

Android elements have white background behind the text on pre-lollipop and lower api versions

无人久伴 提交于 2019-12-11 04:39:57
问题 I use TabLayout for ViewPager <android.support.design.widget.TabLayout android:id="@+id/tabLayout" android:layout_width="match_parent" android:layout_height="wrap_content" app:tabBackground="@drawable/tab_color_selector" /> but here's the result elements with white background at kitkat tab_color_selector has 2 items with state_selected="true" and default. I also tried using tags like theese, but with no success: android:background="@android:color/holo_blue_dark" app:tabBackground="@android