gpt4 book ai didi

android - 无法从 Fragment 中的 ViewModel 观察 LiveData

转载 作者:行者123 更新时间:2023-11-29 22:51:48 25 4
gpt4 key购买 nike

我的 ViewPager 的其中一个 Fragment 中有一个 RecyclerView。此 RecyclerView 显示从服务器获取的数据。它通常可以工作,但我无法使用 ViewModel 和 LiveData 实现相同的功能,因为 livedata.observe 方法不是当 livedataViewModel 更改时被调用。

这是我的 MonthlyOrderViewModel.java 类的源代码

public class MonthlyOrderViewModel extends AndroidViewModel {

private Retrofit retrofit;
private RetrofitServices retrofitServices;
private MutableLiveData<MonthlyOrderHistory> monthlyOrderHistoryMutableLiveData = new MutableLiveData<>();

public MonthlyOrderViewModel(@NonNull Application application) {
super(application);
retrofit = RetrofitFactory.getRetrofit();
retrofitServices = retrofit.create(RetrofitServices.class);
}

public MutableLiveData<MonthlyOrderHistory> getMonthlyOrderHistoryMutableLiveData() {
return monthlyOrderHistoryMutableLiveData;
}
public void fetchMonthlyOrders() {
Call<MonthlyOrderHistory> call = retrofitServices.getAllMonthlyOrderHistory(IpharmaApplication.getInstance().getLoggedInUser().getId());
call.enqueue(new Callback<MonthlyOrderHistory>() {
@Override
public void onResponse(Call<MonthlyOrderHistory> call, Response<MonthlyOrderHistory> response) {

MonthlyOrderHistory monthlyOrderHistory = response.body();
if(monthlyOrderHistory.getStatus().equalsIgnoreCase("success")) {

List<UserOrder> userOrders = monthlyOrderHistory.getOrders().getUserOrder();
if(userOrders != null && userOrders.size() != 0) {
DefaultScheduler.INSTANCE.execute(() -> {
monthlyOrderHistoryMutableLiveData.postValue(monthlyOrderHistory);
return Unit.INSTANCE;
});
}
}
}

@Override
public void onFailure(Call<MonthlyOrderHistory> call, Throwable t) {

t.printStackTrace();
}
});
}

}

DefaultScheduler 是一个 Scheduler,默认情况下处理 AsyncScheduler 中的操作。这是我的 Scheduler.kt 类的源代码


interface Scheduler {

fun execute(task: () -> Unit)

fun postToMainThread(task: () -> Unit)

fun postDelayedToMainThread(delay: Long, task: () -> Unit)
}

//A shim [Scheduler] that by default handles operations in the [AsyncScheduler].
object DefaultScheduler : Scheduler {

private var delegate: Scheduler = AsyncScheduler

//Sets the new delegate scheduler, null to revert to the default async one.
fun setDelegate(newDelegate: Scheduler?) {
delegate = newDelegate ?: AsyncScheduler
}

override fun execute(task: () -> Unit) {
delegate.execute(task)
}

override fun postToMainThread(task: () -> Unit) {
delegate.postToMainThread(task)
}

override fun postDelayedToMainThread(delay: Long, task: () -> Unit) {
delegate.postDelayedToMainThread(delay, task)
}
}

//Runs tasks in a [ExecutorService] with a fixed thread of pools
internal object AsyncScheduler : Scheduler {

private val executorService: ExecutorService = Executors.newFixedThreadPool(NUMBER_OF_THREADS)

override fun execute(task: () -> Unit) {
executorService.execute(task)
}

override fun postToMainThread(task: () -> Unit) {
if (isMainThread()) {
task()
} else {
val mainThreadHandler = Handler(Looper.getMainLooper())
mainThreadHandler.post(task)
}
}

private fun isMainThread(): Boolean {
return Looper.getMainLooper().thread === Thread.currentThread()
}

override fun postDelayedToMainThread(delay: Long, task: () -> Unit) {
val mainThreadHandler = Handler(Looper.getMainLooper())
mainThreadHandler.postDelayed(task, delay)
}
}

//Runs tasks synchronously.
object SyncScheduler : Scheduler {
private val postDelayedTasks = mutableListOf<() -> Unit>()

override fun execute(task: () -> Unit) {
task()
}
override fun postToMainThread(task: () -> Unit) {
task()
}
override fun postDelayedToMainThread(delay: Long, task: () -> Unit) {
postDelayedTasks.add(task)
}
fun runAllScheduledPostDelayedTasks() {
val tasks = postDelayedTasks.toList()
clearScheduledPostdelayedTasks()
for (task in tasks) {
task()
}
}
fun clearScheduledPostdelayedTasks() {
postDelayedTasks.clear()
}
}

最后,我尝试使用以下方法观察 fragment 的 onCreateView 方法的变化:

MonthlyOrderViewModel monthlyOrderViewModel = new MonthlyOrderViewModel(getActivity().getApplication());

monthlyOrderViewModel.getMonthlyOrderHistoryMutableLiveData().observe(this, monthlyOrderHistory -> {

monthlyOrderRecyclerView = view.findViewById(R.id.monthlyOrderRecyclerView);

monthlyOrderRecyclerViewAdapter = new OrderHistoryRecyclerViewAdapter(getContext(), monthlyOrderHistory.getOrders().getUserOrder());

monthlyOrderRecyclerViewAdapter.notifyDataSetChanged();

monthlyOrderRecyclerView.setAdapter(monthlyOrderRecyclerViewAdapter);

monthlyOrderRecyclerView.setLayoutManager(new LinearLayoutManager(getActivity()));

});

我尝试调试一下,发现改造后获取数据没有问题。但是当我尝试在 fragment 中使用它们时,observe 方法永远不会被调用。

请建议我如何解决这个问题?任何帮助将不胜感激。

最佳答案

您不应使用 new 实例化您的 ViewModel。你必须这样做:

MonthlyOrderViewModel monthlyOrderViewModel = ViewModelProviders.of(this).get(MonthlyOrderViewModel.class);

如果您确定 postValue 正在您的 ViewModel 中执行,那么我认为此更改应该使其起作用。还有一件事:每次观察到的 LiveData 通知您发生更改时,您不应该执行所有这些操作。我会将下一行移到 observe()

之前
monthlyOrderRecyclerView = view.findViewById(R.id.monthlyOrderRecyclerView);

monthlyOrderRecyclerViewAdapter = new OrderHistoryRecyclerViewAdapter(getContext(), monthlyOrderHistory.getOrders().getUserOrder());

monthlyOrderRecyclerView.setAdapter(monthlyOrderRecyclerViewAdapter);

monthlyOrderRecyclerView.setLayoutManager(new LinearLayoutManager(getActivity()));

更新

正如 Fahim 在评论中确认的那样,问题在于正在创建同一ViewModel 的多个实例。如果您需要共享 ViewModel 的同一实例,请确保传递作为该 ViewModel“所有者”的 Fragment/Activity 的引用。例如,如果MyActivity有一个MainActivityViewModel并且它包含一个名为MyFragment的子Fragment,那么如果该Fragment想要获取对其父Fragment的引用ViewModel 必须按以下方式执行:

MainActivityViewModel mainActivityVM = ViewModelProviders
.of(getActivity())
.get(MainActivityViewModel.class);

关于android - 无法从 Fragment 中的 ViewModel 观察 LiveData,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/57828575/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com