AsyncTask的neasted或自己的类? [英] AsyncTask neasted or own class?

查看:184
本文介绍了AsyncTask的neasted或自己的类?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这是一般最好的Activitiy中创建的AsyncTask的私有类,或者更确切地说,他们在自己的类分开?

 公共类MyActivity延伸活动{
  私有类DownloadPage扩展的AsyncTask {
  }
}


解决方案

AsyncTask的内部活动是完成任务的研究背景,你可以很容易地改变视图后更为合适。

在单独的类,你需要通过背景及其结果进来单独的类,然后你必须得到独立的类造成的。

但独立的类是非常有用的,有时,当我们需要在应用程序的更多的AsyncTask,
如果你在你的活动有很大的code所以它最好使用独立的类。

所以AsyncTask的适合内的活动与互动观点......而独立的类也
适合当我们需要在应用程序的更多的AsyncTask。

因此​​,它完全取决于需求...

is it in general better to create AsyncTask as private class within an Activitiy, or rather separate them in an own class?

public class MyActivity extends Activity {
  private class DownloadPage extends AsyncTask {
  }
}

解决方案

AsyncTask inside Activity is more suitable after completing backgroud task you can change view easily.

In seperate class you need to pass context and its result comes in seperate class and then you have to get result from seperate class.

But seperate class is very useful sometimes when we need more asyncTask in application , and if you have large code in your activity so its better to use seperate class.

So AsyncTask is suitable inside Activity to interact with view...and seperate class is also suitable when we need more asynctask in application.

So its totally depends on requirements...

这篇关于AsyncTask的neasted或自己的类?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆