Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add info about using 'autoscrollviewpager' lib with support-v13 lib #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AlexTrotsenko
Copy link

I am using "native" fragments instead of android.support.v4.app.Fragment and target 4.1 only. That's why I only have

    compile 'com.android.support:appcompat-v7:21.0.+'
    compile 'com.android.support:support-v13:21.0.+' 
    compile 'com.viewpagerindicator:library:2.4.1@aar'

When I just add

   compile 'cn.trinea.android.view.autoscrollviewpager:android-auto-scroll-view-pager:1.1.2'

I have compilation errors like this:

.../.../Fragment.java:233: error: cannot find symbol
            final View switchContainer = MenuItemCompat.getActionView(filtersMenuItem);
                                                       ^
  symbol:   method getActionView(MenuItem)
  location: class MenuItemCompat

.../.../Fragment.java:291: error: cannot find symbol
            MenuItemCompat.setOnActionExpandListener(searchItem, new MenuItemCompat.OnActionExpandListener() {
                                                                                   ^
  symbol:   class OnActionExpandListener
  location: class MenuItemCompat

I assume, that it's because of conflicts of support-v13 and support-v4 libs.

Anyway, when I remove support-v4 lib from dependency of android-auto-scroll-view-pager lib, then all errors disappear. I guess, it's worth to add this information to 1st readme page. It could safe some hours for another people, who have same configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant