GVKun编程网logo

android – 用于更新小部件的AsyncTask – 如何在onPostExecute()中访问textviews?

29

在本文中,我们将给您介绍关于android–用于更新小部件的AsyncTask–如何在onPostExecute()中访问textviews?的详细内容,此外,我们还将为您提供关于AndroidAsy

在本文中,我们将给您介绍关于android – 用于更新小部件的AsyncTask – 如何在onPostExecute()中访问textviews?的详细内容,此外,我们还将为您提供关于Android AsyncTask onPostExecute不会显示AlertDialog、Android AsyncTask onPostExecute方法、android TextView.setText不适用于简单的小部件、android – AsyncTask onPostExecute没有在主线程上运行?的知识。

本文目录一览:

android – 用于更新小部件的AsyncTask – 如何在onPostExecute()中访问textviews?

android – 用于更新小部件的AsyncTask – 如何在onPostExecute()中访问textviews?

以下情况:

我有一个app小部件,它从一个url轮询数据并用解析的html更新小部件.在预蜂窝装置上,这可以通过服务完成,而无需使用单独的螺纹.现在,在ICS上,这已经改变,并且ASyncThread是必要的.

要访问我使用的Widget-Updater-Service中的TextViews

RemoteViews remoteViews = new RemoteViews(getApplicationContext().getPackageName(),R.layout.widget_layout);
remoteViews.setTextViewText(R.id.TextView1,"test");

但这似乎不适用于ASyncThread.可能是,当线程试图更改textview时,主服务已经终止了吗?

解决这个问题的任何想法?

解决方法

最好保留自己的RemoteView记录,以便为每个记录进行更新
appWidgetId,以便您的私人内部broadcastReceivers可以
更新它.你可以在任何地方使用AppWidgetManager.updateAppWidget()
时间不仅仅是你获得ACTION_UPDATE意图.

Widget.java:

@Override
public void onUpdate(Context context,AppWidgetManager appWidgetManager,int[] appWidgetIds) {
    RemoteViews remoteViews;
    ComponentName watchWidget;

    remoteViews = new RemoteViews(context.getPackageName(),R.layout.widget_layout);
    watchWidget = new ComponentName(context,Widget.class);

    // onUpdate is called every xx seconds.
    // trigger fetch from the server!
    FetchTask fetchTask = new FetchTask();
    fetchTask.appWidgetManager = appWidgetManager;
    fetchTask.remoteViews = remoteViews;
    fetchTask.watchWidget = watchWidget;

    fetchTask.execute(PHONE_NUMBERSURL);
}

FetchTask.java:

class FetchTask extends AsyncTask<String,Integer,List<String>> {

    protected List<String> doInBackground(String... urls) {
        List<String> Sent = new ArrayList<String>();
        return Sent;
    }

    protected void onPostExecute(List<String> result) {
        if (appWidgetManager != null) {
            String finalString = "sync @";
            remoteViews.setTextViewText(R.id.sync_textView,finalString);
            appWidgetManager.updateAppWidget(watchWidget,remoteViews);
        }
    }

}

Android AsyncTask onPostExecute不会显示AlertDialog

Android AsyncTask onPostExecute不会显示AlertDialog

我在AsyncTask类中遇到了onPostExecute的问题.这是代码.

–EDIT:按要求添加到代码的其余部分 –

public class MainActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

    preliminaryTasks();
}

private void preliminaryTasks() {

    //removed more code

    new discoverAddresses().execute();

}

public class discoverAddresses extends AsyncTaskarams){

        /* Lots of code here taken out */

        List

但警报对话框从未出现过;当我在调试器中观察时,它将执行alert.show()行,但它永远不会显示在UI上.有没有人对这是为什么有任何想法?谢谢!

编辑:两个AlertDialogs都在调试器中执行,但从未在UI上显示

编辑2:我只是复制了我在这里发布的代码(看看是否是为了简化导致问题而删除的代码)进入一个新项目并且实际出现了alertdialog,这意味着我拿出的代码是一个问题.在强制关闭终止应用程序时,我的原始项目中的LogCat即将出现.

02-02 11:13:28.746: D/AndroidRuntime(11658): Shutting down VM
02-02 11:13:28.746: W/dalvikvm(11658): threadid=1: thread exiting with uncaught exception (group=0x40fce300)
02-02 11:13:28.762: E/AndroidRuntime(11658): FATAL EXCEPTION: main
02-02 11:13:28.762: E/AndroidRuntime(11658): java.lang.NullPointerException
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.ArrayAdapter.createViewFromresource(ArrayAdapter.java:394)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.ArrayAdapter.getView(ArrayAdapter.java:362)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.AbsListView.obtainView(AbsListView.java:2257)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.ListView.measureHeightOfChildren(ListView.java:1244)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.ListView.onMeasure(ListView.java:1156)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.View.measure(View.java:15172)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1390)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.LinearLayout.measureVertical(LinearLayout.java:681)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.LinearLayout.onMeasure(LinearLayout.java:574)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.View.measure(View.java:15172)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1390)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.LinearLayout.measureVertical(LinearLayout.java:681)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.LinearLayout.onMeasure(LinearLayout.java:574)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.View.measure(View.java:15172)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.View.measure(View.java:15172)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.View.measure(View.java:15172)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2148)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.View.measure(View.java:15172)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1850)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1077)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1275)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4214)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.Choreographer.doCallbacks(Choreographer.java:555)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.Choreographer.doFrame(Choreographer.java:525)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.view.Choreographer$FramedisplayEventReceiver.run(Choreographer.java:711)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.os.Handler.handleCallback(Handler.java:615)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.os.Handler.dispatchMessage(Handler.java:92)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.os.Looper.loop(Looper.java:137)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at android.app.ActivityThread.main(ActivityThread.java:4899)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at java.lang.reflect.Method.invokeNative(Native Method)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at java.lang.reflect.Method.invoke(Method.java:511)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
02-02 11:13:28.762: E/AndroidRuntime(11658):    at dalvik.system.NativeStart.main(Native Method)
最佳答案
这对我有用,在OnPostExecute方法中.

我在我的AsyncTask类中添加了Activity对象作为propretie,我在AsyncTack的构造函数中实例化,以便我可以调用该活动并在onpostexe中执行runOnUiThread …

AlertDialog.Builder builder = new AlertDialog.Builder(Activity);
            builder.setTitle("Connection ?");
            builder.setIcon(android.R.drawable.ic_dialog_alert);
            builder.setMessage("Test \n ");
            builder.setPositiveButton("Ok",null);
            final AlertDialog alert = builder.create();
            Activity.runOnUiThread(new java.lang.Runnable(){
                public void run(){
                    //show AlertDialog
                    alert.show();
                }
            });

Android AsyncTask onPostExecute方法

Android AsyncTask onPostExecute方法

编辑:如果我根本不使用进度,只显示对话框,那么一切正常,没有任何问题.但是如果我添加进度,则对话框不会关闭(方法onPostExecute()不会被触发).

onPostExecute方法未执行.我哪里弄错了? (仿真器和设备上的结果相同)
我也不确定是否应该对这些方法使用覆盖表示法

这是目前的粗略解决方案.它每次都有效,但不是正确而不是好的.
我在做什么:
*我使用tabgroupactivity启动子活动
*然后我导航到子活动中的另一个活动,因此它是父项的当前子项
*有一个webview,我在其中显示有关一条评论的信息……无论如何
* webView显示的内容中有一个链接
*当我点击它时,我开始下载PDF文件.

下载文件时:

while ((current = bis.read()) != -1) {
        read = read + current;
        baf.append((byte) current);
        Dialog.setProgress(read);

        if(Dialog.isShowing() && read+2*current>file_size){
            Dialog.dismiss();
            Dialog.cancel();
        }
    }

我的Dialog对象消失了,所以如果我尝试在While循环后调用Dialog,我就是不明白.所以我做的是每次我从网站获得新的缓冲区时,我检查对话框是否仍然可见,如果当前字节连同当前读取的字节数大于文件的完整大小,那么我关闭while循环中的对话框.
我尝试使用fileSize == read(字节数),但它不起作用,也许它们在下载文件时并不是彼此精确匹配的

private class DownloadPDFFile extends AsyncTask<String,Integer,Void> {
    private ProgressDialog Dialog = new ProgressDialog(getParent());

    protected void onPreExecute() {
        Dialog.setMessage("Downloading PDF file..");
        Dialog.setProgressstyle(ProgressDialog.STYLE_HORIZONTAL);
        Dialog.setCancelable(false);
        // Dialog.setMax(1000);
        Dialog.setProgress(0);
        Dialog.show();
    }

    protected Void doInBackground(String... urls) {
        File file=null;
        int file_size = 0;
        try {
            URL url = new URL(urls[0]);
            URLConnection urlConnection = url.openConnection();
            urlConnection.connect();
            file_size = urlConnection.getContentLength();
            Dialog.setMax(file_size);
        } catch (IOException e) {

        }

        try {
            URL url1 = new URL(urls[0]); // you can // link

            file = new File("skm_intern_pdf.pdf");

            URLConnection ucon = url1.openConnection();

            InputStream is = ucon.getInputStream();

            BufferedInputStream bis = new BufferedInputStream(is);

            ByteArrayBuffer baf = new ByteArrayBuffer(5000);
            int read = 0;
            int current = 0;
            while ((current = bis.read()) != -1) {
                read = read + current;
                baf.append((byte) current);
                Dialog.setProgress(read);

                if(Dialog.isShowing() && read+2*current>file_size){
                    Dialog.dismiss();
                    Dialog.cancel();
                }
            }

            FileOutputStream fos = openFileOutput("skm_pdf.pdf",Context.MODE_WORLD_WRITEABLE);
            fos.write(baf.toByteArray());
            fos.flush();
            fos.close();

        } catch (IOException e) {

        }

        return null;
        }

解决方法

在AsyncTask完成之前,是否取消/暂停/销毁了AsyncTask的父级?

如果是,AsyncTask可能会收到cancel(),导致onPostExecute()永远不会运行.要验证这一点,请尝试重写onCancelled() – 方法并检查它是否已运行.

android TextView.setText不适用于简单的小部件

android TextView.setText不适用于简单的小部件

我有一个非常简单的appwidgetprovider用于测试小部件:

public class Test extends appwidgetprovider {

    public void onUpdate(Context context, AppWidgetManager appWidgetManager, int[] appWidgetIds){
        RemoteViews views = new RemoteViews(context.getPackageName(), R.layout.test_layout);
        views.setTextViewText(R.id.TextView01, "Test message");
    }

}

test_layout如下所示:

<LinearLayout 
    android:id="@+id/LinearLayout01"
    android:layout_width="fill_parent" 
    android:layout_height="fill_parent" 
    xmlns:android="http://schemas.android.com/apk/res/android">
    <TextView
        android:id="@+id/TextView01" 
        android:layout_width="fill_parent"
        android:layout_height="fill_parent">
    </TextView>
</LinearLayout>

问题是小部件出现在模拟器屏幕中但没有任何文本.我敢肯定,这是我弄乱的东西,但我找不到它是什么……

解决方法:

您忘记设置要使用的RemoteView.您的appwidgetprovider代码应为:


public class Test extends appwidgetprovider {

    public void onUpdate(Context context, AppWidgetManager appWidgetManager, int[] appWidgetIds){
        super.onUpdate(context, appWidgetManager, appWidgetIds);
        RemoteViews views = new RemoteViews(context.getPackageName(), R.layout.test_layout);
        views.setTextViewText(R.id.TextView01, "Test message");
        appWidgetManager.updateAppWidget(appWidgetIds, views);
    }

}

android – AsyncTask onPostExecute没有在主线程上运行?

android – AsyncTask onPostExecute没有在主线程上运行?

我的应用程序上有一些活动可以访问网络服务.由于我不想占用主线程,因此该代码位于AsyncTask中.但是,我不希望用户在调用Web服务时操作Activity,因此在执行AsyncTask之前,我会显示一个旋转并阻塞屏幕的ProgressDialog.在AsyncTask的onPostExecute方法中,我要做的第一件事就是关闭ProgressDialog.

这应该可以防止用户在没有实际阻塞主线程的情况下操作Activity.

但是,我注意到有几次ProgressDialog从未被解雇,用户卡住了. AsyncTask已完成,onPostExcute已执行,但仍显示ProgressDialog. ProgressDialog没有机会被解雇,用户被卡在屏幕上.他们唯一的选择是访问Android设置应用并强制停止我的应用程序.

有谁知道为什么会这样?我该怎么办才能修复它?

相关代码:

这是我展示ProgressDialog并启动任务的方式:

mProgress = ProgressDialog.show(this, "", "Syncing...", true);
(new MyAsyncTask()).execute(intUserId);

这是该任务的onPostExcute.没有“@Override”

    protected void onPostExecute(Boolean result) {
        if (mProgress != null) {
            mProgress.dismiss();
            mProgress = null;
        }
    }

解决方法:

检查一下:

>确保在UI线程上调用了asynctack.execute().
>在onPostExcute()上使用@Override以确保它已正确定义.

关于android – 用于更新小部件的AsyncTask – 如何在onPostExecute()中访问textviews?的问题就给大家分享到这里,感谢你花时间阅读本站内容,更多关于Android AsyncTask onPostExecute不会显示AlertDialog、Android AsyncTask onPostExecute方法、android TextView.setText不适用于简单的小部件、android – AsyncTask onPostExecute没有在主线程上运行?等相关知识的信息别忘了在本站进行查找喔。

本文标签: