Android P visibilityawareimagebutton.setVisibility 只能从同一个库组调用

Android P visibilityawareimagebutton.setVisibility can only be called from the same library group

我正在尝试使用新的 Android P FloatingActionButton,它是 com.google.android.material.floatingactionbutton.FloatingActionButton 的一部分,但我收到此警告:

VisibilityAwareImageButton.setVisibility can only be called from the same library group (groupId=com.google.android.material)

import com.google.android.material.floatingactionbutton.FloatingActionButton
import android.view.View

class MainActivity : AppCompatActivity() {

    lateinit var demoFab: FloatingActionButton

    override fun onCreate(savedInstanceState: Bundle?) {
        demoFab = findViewById(R.id.demoFab)
        demoFab.visibility = View.VISIBLE  // the warning is here
    }
}

我试过搜索,唯一的搜索结果是关于响应 UI 可见性变化:

Respond to UI visibility changes

我试着探索如何查看 com.google.android.material 包中是否有 VISIBLE int 值,我发现的唯一一个是 com.google.android.material.floatingactionbutton.FloatingActionButton.VISIBLE,但警告仍然存在.

顶级build.gradle

buildscript {
    ext.kotlin_version = '1.2.41'
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.2.0-alpha14'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath "com.google.gms:oss-licenses:0.9.2"
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        jcenter()
        mavenCentral()
        maven { url "http://oss.sonatype.org/content/repositories/snapshots/" }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

项目级build.gradle

apply plugin: 'com.android.application'

apply plugin: 'kotlin-android'

apply plugin: 'kotlin-android-extensions'

apply plugin: 'com.google.gms.oss.licenses.plugin'

android {
    compileSdkVersion 'android-P'
    defaultConfig {
        applicationId "com.codeforsanjose.maps.pacmap"
        minSdkVersion 21
        targetSdkVersion 'P'
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }
    splits {
        abi {
            enable true
            reset()
            include 'arm64-v8a', 'armeabi', 'armeabi-v7a', 'mips', 'x86', 'x86_64'
            universalApk false
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    buildTypes {
        release {
            minifyEnabled true
            shrinkResources true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    implementation 'androidx.appcompat:appcompat:1.0.0-alpha1'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.0'
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.0-alpha2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0-alpha2'

    implementation 'com.mapbox.mapboxsdk:mapbox-android-sdk:5.5.2'
    //implementation 'com.mapbox.mapboxsdk:mapbox-android-sdk:6.1.0'
    implementation 'com.mapbox.mapboxsdk:mapbox-android-plugin-locationlayer:0.5.0'
    implementation 'com.mapbox.mapboxsdk:mapbox-android-navigation:0.13.0'
    implementation 'com.mapbox.mapboxsdk:mapbox-android-navigation-ui:0.13.0'

    implementation 'com.google.android.gms:play-services-oss-licenses:15.0.1'
    implementation 'com.google.code.gson:gson:2.8.2'
    implementation 'com.squareup.moshi:moshi:1.5.0'
    implementation 'com.squareup.okhttp3:logging-interceptor:3.10.0'
    implementation 'com.squareup.retrofit2:converter-gson:2.3.0'
    implementation 'com.squareup.retrofit2:converter-moshi:2.4.0'
    implementation "com.squareup.retrofit2:adapter-rxjava2:2.3.0"
    implementation 'com.squareup.retrofit2:retrofit:2.4.0'
    implementation 'io.reactivex.rxjava2:rxandroid:2.0.1'
    implementation 'io.reactivex.rxjava2:rxkotlin:2.2.0'
}

编辑:

请注意,我使用的是 Android Studio 版本 3.2 canary 14。似乎已报告此版本的一些错误,我怀疑这是其中之一。

编辑 2:

问题仍然存在于 Android Studio 版本 3.2 canary 15,但我使用 show()hide()

找到了解决方法
override fun onCreate(savedInstanceState: Bundle?) {
    demoFab = findViewById(R.id.demoFab)
    demoFab.show()    // this works and doesn't have the warning
}

使用方法 1

demoFab.show(); // in place of visible
demoFab.hide(); // in place of Invisible suppress the warning/error for me.

和方法 2

@SuppressLint("RestrictedApi") // also suppressed the warning
private void setUp() {
    ....
}

更新:

方法三:

demoFab.setVisibility(View.GONE);
demoFab.setVisibility(View.INVISIBLE);
demoFab.setVisibility(View.VISIBLE);

方法四:

demoFab.visibility = View.GONE
demoFab.visibility = View.INVISIBLE
demoFab.visibility = View.VISIBLE

将其转换为视图似乎工作正常。

(mFloatingActionButton as View).visibility = INVISIBLE

当然你需要记住,可见性可能会影响其他组件,所以你应该同时使用 show()hide() 以确保其他组件收到更改通知。

这也有效:

findViewById(R.id.fab).setVisibility(View.GONE);

对于 Kotlin 我有一个扩展方法

fun viewsVisibility(visibility: Int, vararg views: View) {
    for (view in views) { view.visibility = visibility }
}

然后在代码中您可以执行以下操作

viewsVisibility(View.VISIBLE, demoFab) 
viewsVisibility(View.GONE, demoFab)
viewsVisibility(View.INVISIBLE, demoFab, addFab, removeFab)

错误将消失,这为任何可见性状态提供了灵活性,同时接受要处理的视图列表。很多时候我需要一次处理多个视图,如最后一行所示。

使用:

 myButton.hide();
 myClearButton.hide();

一个典型的例子是:

在用户键入或关注 EditText 资源时隐藏和显示按钮:

检查用户是否正在输入或是否有焦点:

 mCommentField.setOnFocusChangeListener(new View.OnFocusChangeListener() {
        @Override
        public void onFocusChange(View view, boolean hasFocus) {
            if (hasFocus) {
                //user has focused
                showBts();

            } else {
                //focus has stopped perform your desired action
                hideButtons();
            }
        }


    });

隐藏和显示按钮方法:

private void hideButtons() {

    mCommentButton.hide();
    mClearButton.hide();
}

private void showBts() {

    mCommentButton. show();
    mClearButton.show();

并且在您的 xml 中,将按钮默认设置为不可见,以便它们仅 display/show 当用户获得焦点或正在键入时:

android:visibility="invisible"

最佳实践:

 android:visibility="Gone"

使用 visibility gone 意味着您的视图不会占用布局上的任何 space 而 "invisible" 将占用布局上不必要的 space

在此 example:My 中,视图位于 ViewHolder 中,并且我使用 recylerview

引用片段中的按钮
if(data){
            fragmentPendingApprovalDetailsBinding.fabPendingList.show();
        }else {
            fragmentPendingApprovalDetailsBinding.fabPendingList.hide();
        }

对于com.google.android.material.floatingactionbutton.FloatingActionButton

能见度

使用显示和隐藏方法为 FloatingActionButton 的可见性设置动画。 show 动画放大 widget 并使其淡入,而 hide 动画缩小 widget 并使其淡出。

来源:https://material.io/develop/android/components/floating-action-button/

对于android.support.design.widget.FloatingActionButton 使用setVisibility()方法

对我来说,上述方法不起作用,所以我创建了一个扩展函数来使其起作用。

fun View.showView() {
    this.visibility = View.VISIBLE
}

fun View.hideView() {
    this.visibility = View.GONE
}

现在打电话给

binding.fabAdded.showView()