当4个EditText的字符数超过X个且电子邮件有效(忽略xml,仍在应用样式)时,我尝试启用/禁用按钮:
<Button
android:id="@+id/fragment_login_button"
android:fontFamily="@font/montserrat_regular"
android:layout_marginTop="20dp"
android:textColor="@android:color/white"
android:background="@drawable/button_primary"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_marginLeft="20dp"
android:enabled="@{viewModel.createAccountDetailsValid}"
android:layout_marginRight="20dp"
android:text="create account "
android:onClick="@{(theView) -> handler.onCreateClick(theView, viewModel)}"
app:layout_constraintTop_toBottomOf="@id/fragment_login_companyText"
/>
我使用了按钮所依赖的 MediatorLiveData和4 MutableLiveData ,但是我发现这样做会违反MVVM标准,但是这是它唯一的工作方式,因为MediatorLiveData仅允许具有至少1个观察者的addSource,请查看代码:
在我的视图模型上:
//USER DATA
val email: MutableLiveData<String> = MutableLiveData()
val name: MutableLiveData<String> = MutableLiveData()
val surname: MutableLiveData<String> = MutableLiveData()
val company: MutableLiveData<String> = MutableLiveData()
val createAccountDetailsValid: MediatorLiveData<Boolean> = MediatorLiveData()
fun populateMediator(owner: LifecycleOwner) {
createAccountDetailsValid.observe(owner, Observer { })
createAccountDetailsValid.addSource(email) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
createAccountDetailsValid.addSource(name) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
createAccountDetailsValid.addSource(surname) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
createAccountDetailsValid.addSource(company) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
}
private fun isCreateAccountDetailsValid() : Boolean {
if(email.value == null || name.value == null || surname.value == null || company.value == null) return false
return android.util.Patterns.EMAIL_ADDRESS.matcher(email?.value!!).matches() && name.value?.length!! >= 3 && surname.value?.length!! >= 3 && company.value?.length!! >= 3
}
关于我的片段:
override fun onCreateView(
inflater: LayoutInflater, container: ViewGroup?,
savedInstanceState: Bundle?
): View? {
binding = DataBindingUtil.inflate(inflater, R.layout.fragment_login, container,false)
viewModel = ViewModelProviders.of(this, viewModelFactory).get(LoginViewModel::class.java)
binding.viewModel = viewModel
binding.handler = LoginHandler()
binding.setLifecycleOwner(this)
viewModel.setLifecycleOwner(this as LifecycleOwner)
return binding.root
}
就像我说的那样,但是ViewModel引用了View(LifecycleOwner),是的,我可以将空的观察者放在Fragment上,不需要将LifecycleOwner传递给ViewModel,但仍然感觉不合适,也许我在这里有点完美主义者,但我敢打赌,还有一种直接从ViewModel进行绑定的方法,而不必必须设置isEnable来观察Fragment中的MediatorLiveData?
谢谢!
答案 0 :(得分:0)
有Blackbelt评论,我应该做错了事,最终使问题变得复杂并解决了,同时试图使其正常工作。
他说过可以观察到数据绑定,并且可以像我一样在viewModel初始化上添加Source并使其起作用:
val createAccountResult: MutableLiveData<Resource<Void>> = MutableLiveData()
val loginResult: MutableLiveData<Resource<Void>> = MutableLiveData()
//USER DATA
val email: MutableLiveData<String> = MutableLiveData()
val name: MutableLiveData<String> = MutableLiveData()
val surname: MutableLiveData<String> = MutableLiveData()
val company: MutableLiveData<String> = MutableLiveData()
var createAccountDetailsValid: MediatorLiveData<Boolean> = MediatorLiveData()
init {
createAccountDetailsValid.addSource(email) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
createAccountDetailsValid.addSource(name) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
createAccountDetailsValid.addSource(surname) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
createAccountDetailsValid.addSource(company) {
createAccountDetailsValid.value = isCreateAccountDetailsValid()
}
}
感谢您@Blackbelt的帮助