当前位置: 首页>>代码示例>>Java>>正文


Java Request.clear方法代码示例

本文整理汇总了Java中com.bumptech.glide.request.Request.clear方法的典型用法代码示例。如果您正苦于以下问题:Java Request.clear方法的具体用法?Java Request.clear怎么用?Java Request.clear使用的例子?那么, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在com.bumptech.glide.request.Request的用法示例。


在下文中一共展示了Request.clear方法的3个代码示例,这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞,您的评价将有助于系统推荐出更棒的Java代码示例。

示例1: clearRemoveAndMaybeRecycle

import com.bumptech.glide.request.Request; //导入方法依赖的package包/类
private boolean clearRemoveAndMaybeRecycle(@Nullable Request request, boolean isSafeToRecycle) {
   if (request == null) {
     // If the Request is null, the request is already cleared and we don't need to search further
     // for its owner.
    return true;
  }
  boolean isOwnedByUs = requests.remove(request);
  // Avoid short circuiting.
  isOwnedByUs = pendingRequests.remove(request) || isOwnedByUs;
  if (isOwnedByUs) {
    request.clear();
    if (isSafeToRecycle) {
      request.recycle();
    }
  }
  return isOwnedByUs;
}
 
开发者ID:weiwenqiang,项目名称:GitHub,代码行数:18,代码来源:RequestTracker.java

示例2: untrackOrDelegate

import com.bumptech.glide.request.Request; //导入方法依赖的package包/类
private void untrackOrDelegate(Target<?> target) {
  boolean isOwnedByUs = untrack(target);
  // We'll end up here if the Target was cleared after the RequestManager that started the request
  // is destroyed. That can happen for at least two reasons:
  // 1. We call clear() on a background thread using something other than Application Context
  // RequestManager.
  // 2. The caller retains a reference to the RequestManager after the corresponding Activity or
  // Fragment is destroyed, starts a load with it, and then clears that load with a different
  // RequestManager. Callers seem especially likely to do this in retained Fragments (#2262).
  //
  // #1 is always an error. At best the caller is leaking memory briefly in something like an
  // AsyncTask. At worst the caller is leaking an Activity or Fragment for a sustained period of
  // time if they do something like reference the Activity RequestManager in a long lived
  // background thread or task.
  //
  // #2 is always an error. Callers shouldn't be starting new loads using RequestManagers after
  // the corresponding Activity or Fragment is destroyed because retaining any reference to the
  // RequestManager leaks memory. It's possible that there's some brief period of time during or
  // immediately after onDestroy where this is reasonable, but I can't think of why.
  if (!isOwnedByUs && !glide.removeFromManagers(target) && target.getRequest() != null) {
    Request request = target.getRequest();
    target.setRequest(null);
    request.clear();
  }
}
 
开发者ID:weiwenqiang,项目名称:GitHub,代码行数:26,代码来源:RequestManager.java

示例3: clearRemoveAndRecycle

import com.bumptech.glide.request.Request; //导入方法依赖的package包/类
/**
 * Stops tracking the given request, clears, and recycles it, and returns {@code true} if the
 * request was removed or {@code false} if the request was not found.
 */
public boolean clearRemoveAndRecycle(Request request) {
  boolean isOwnedByUs =
      request != null && (requests.remove(request) || pendingRequests.remove(request));
  if (isOwnedByUs) {
    request.clear();
    request.recycle();
  }
  return isOwnedByUs;
}
 
开发者ID:weiwenqiang,项目名称:GitHub,代码行数:14,代码来源:RequestTracker.java


注:本文中的com.bumptech.glide.request.Request.clear方法示例由纯净天空整理自Github/MSDocs等开源代码及文档管理平台,相关代码片段筛选自各路编程大神贡献的开源项目,源码版权归原作者所有,传播和使用请参考对应项目的License;未经允许,请勿转载。