In parts 1-3 of this series, I have explored three different means for an Android non-UI thread to communicate user interface updates to the UI thread. The links below are to the series posts.

In this fourth installment, I want to show you how to use a broadcasts and a broadcast receiver to provide non-UI to UI thread communications.

BACKGROUND NON-UI THREAD TO UI THREAD COMMS

As background for those jumping into the middle of this series, non user interface (UI) threads are not allowed to make updates to the UI.  For example, using a non-UI thread to update a TextView’s displayed text results in a CalledFromWrongThreadException.  However, trying to do too much work (as defined as not allowing the user to interact with the UI for more than 5 seconds) on the UI thread leads to Android Not Responsive errors.  So you need to have non-UI threads perform larger/bigger computing tasks, but need those threads to be able to communicate updates back to the UI thread to perform display updates.

In the first three posts, I showed how to use an activity’s runOnUiThread() method, a view component’s post() method, and the Android Handler Framework to have the non-UI thread send a user interface update request back to the UI thread for display.  Each of these past three options take advantage of the underlying UI event message channel to message the UI thread to perform the user interface update.  In this post, I show you a different means of providing the communications via broadcast intent that is acted on by a BroadcastReceiver on the UI thread.

SIMPLE APP

A simple application (called Simple App) will again be used to demonstrate the use of broadcast messages for thread communications.  The app has two buttons to start/stop a non-UI thread.  The non-UI thread’s job is to simulate long running work by generating a random number, call the UI to have a TextView widget update the display of the random number, and then sleep for a number of seconds.

The application code for this simple example is provided here.

OPTION 4 – USING A BROADCAST

Broadcasts are Android Intents that indicate some action has occurred.  Some broadcasts are system broadcasts.  For example, one of the built in Android broadcast is that the battery is low.  You can create your own custom broadcasts as well.

Broadcast receivers are components in the application that listen for broadcasts and take some action.  You could, for example, build a broadcast receiver to listen for the battery getting low broadcast event in order to inform the user that unsaved data should be saved quickly.  Of course, you can also build a broadcast receiver to listen for your own custom application broadcasts.

So, a broadcast and broadcast receiver can be used to accomplish the non-UI to UI thread communications.  The non-UI thread can publish a broadcast intent that a broadcast receiver associated to the UI thread uses to perform the UI update.

Now, per the Android documentation on BroadcastReceivers, if your custom application broadcasts are not going to be used across applications, you should consider using a LocalBroadcastManager to send a local broadcast versus a system broadcast.  A LocalBroadcastManager’s intent broadcasts are not broadcast to other applications.  They are therefore a bit more efficient and secure than using a general broadcast message.  You can read a prior blog postof mine to learn more about LocalBroadcastManager and local broadcasts.

Therefore, given the fact that the non-UI to UI thread communication is local to your application, I would recommend (and will show below) using the LocalBroadcastManager to perform the thread communications.

PUBLISHING THE BROADCAST

First, from the non-UI thread, create an Intent that provides the necessary information to the UI thread about the user interface updates that are required.  In this example, the non-UI thread simply provides the new random number that was generated as extra data (under the key of “result”) in the Intent.  Then use an instance of Android’s LocalBroadcastManager to send the local broadcast.

 
1
2
3
Intent intent = new Intent("com.intertech.random.generation");
intent.putExtra("result", text);
LocalBroadcastManager.getInstance(ShowSomethingActivity.this).sendBroadcast(intent);
SET A BROADCAST RECEIVER LISTENING

On the UI thread, you need to create an instance of BroadcastReceiver to listen for updates coming from the non-UI thread.  In this simple application, I created an anonymous BroadcastReceiver instance from within the createBroadcastRecevier() method which is called from the onCreate( ) method of the application’s main activity.

 
1
2
3
4
5
6
7
8
private BroadcastReceiver createBroadcastReceiver() {
  return new BroadcastReceiver() {
    @Override
    public void onReceive(Context context, Intent intent) {
      updateResults(intent.getStringExtra("result"));
    }
  };
}

The updateResults() method of the broadcast receiver gets the TextView and updates the string with what is in the broadcast’s extra data at “result”.

Once the broadcast receiver is created in onCreate(), use a LocalBroadcastManager to register the UI thread for the broadcasts sent by the non-UI thread, specifically those with the string action of “com.intertech.random.generation”);

 
1
2
3
4
5
6
7
8
9
@Override
protected void onCreate(Bundle savedInstanceState) {
  ...
 
  resultReceiver = createBroadcastReceiver();
  LocalBroadcastManager.getInstance(this).registerReceiver(resultReceiver, new IntentFilter("com.intertech.random.generation"));
 
  ...
}

Now, once the non-UI thread publishes its local broadcast, the broadcast receiver listening for the message gets the Intent and takes on the responsibility of updating the UI on the UI thread.

As a last bit of housekeeping, make sure to unregister the broadcast receiver when the communication between non-UI and UI threads is no longer needed.  In this example, I unregister the BroadcastReceiver in the onDestroy() method of the main activity.

 
1
2
3
4
5
6
7
@Override
protected void onDestroy() {
  if (resultReceiver != null) {
    LocalBroadcastManager.getInstance(this).unregisterReceiver(resultReceiver);
  }
  super.onDestroy();
}
CONSIDERATIONS OF OPTION 4 – BROADCASTS

The broadcast option is not reliant on the message event queue.  Instead it relies on a different Android set of components; namely the Intent and Intent listener called a broadcast receiver.  This sub-framework has pluses and minuses.  There are no convenience methods as provided through methods like post() and runOnUiThread() using the thread’s event queue.  Some consider working with Intents, BroadcastReceivers (and LocalBroadcastManager) a bit more complex.  However, the broadcast intent can conveniently carry quite a bit of data to the UI thread from the non-UI thread.  Also importantly, the non-UI thread and UI thread do not have to share any component knowledge.  So the non-UI thread is quite decoupled from the UI thread.  The only information shared by the two threads is the name of the intent action.

WRAP UP

Just one more post in this series.  In that post, I’ll show you how to use an AsyncTask’s for do long running work on a separate non-UI thread, while still being able to push changes to the UI via special UI thread methods.

Please connect with Intertechif you or your organization could use help on your Android/mobile project.

Read more: http://www.intertech.com/Blog/android-non-ui-to-ui-thread-communications-part-4-of-5/#ixzz3Myuoh9Jf 
Follow us: @IntertechInc on Twitter | Intertech on Facebook

android-non-ui-to-ui-thread-communications-part-4-of-5的更多相关文章

  1. Android Non-UI to UI Thread Communications(Part 3 of 5)

    Original:http://www.intertech.com/Blog/android-non-ui-to-ui-thread-communications-part-3-of-5/ Conti ...

  2. Android Non-UI to UI Thread Communications(Part 2 of 5)

    Original:http://www.intertech.com/Blog/android-non-ui-to-ui-thread-communications-part-2-of-5/ his i ...

  3. Android子线程更新UI成功

    android子线程更新UI成功 今天在写demo的时候,在子线程中更新UI,发现更新成功,记录一下. protected void onCreate(Bundle savedInstanceStat ...

  4. Android Phonebook编写联系人UI加载及联系人保存流程(一)

    2014-01-06 17:05:11 将百度空间里的东西移过来. 本文适合ROM定制做Phonebook的童鞋看,其他人飘过即可- Phonebook添加/编辑联系人UI加载及保存联系人流程,是一系 ...

  5. 50个Android开发人员必备UI效果源码[转载]

    50个Android开发人员必备UI效果源码[转载] http://blog.csdn.net/qq1059458376/article/details/8145497 Android 仿微信之主页面 ...

  6. 【Android】11.0 UI开发(二)——列表控件ListView的简单实现1

    ************************ 转载请注明出处:https://www.cnblogs.com/xiaofu007/p/10342462.html ***************** ...

  7. 重大发现: windows下C++ UI库 UI神器-SOUI(转载)

    转载:http://www.cnblogs.com/setoutsoft/p/4996870.html 在Windows平台上开发客户端产品是一个非常痛苦的过程,特别是还要用C++的时候.尽管很多语言 ...

  8. 转: windows下C++ UI库 UI神器-SOUI

    转:http://www.cnblogs.com/setoutsoft/p/4996870.html 前言 在Windows平台上开发客户端产品是一个非常痛苦的过程,特别是还要用C++的时候.尽管很多 ...

  9. 小波说雨燕 第三季 构建 swift UI 之 UI组件集-视图集(六)Picker View视图 学习笔记

    想对PickerView进行操作,只能在代码中操作. 下面 ,再添加三个label组件,然后将所有组件配置到代码中(看代码),然后要实现对PickerView的操作,就要实现它的DataSource协 ...

  10. 【译】UI设计基础(UI Design Basics)--导航(Navigation)(六)

    [译]UI设计基础(UI Design Basics)--导航(Navigation)(六)

随机推荐

  1. 获得N位数字字母随机组合

    import string import random def get_rand(n): allw = string.letters+string.digits r = [] for i in ran ...

  2. js jquery 判断IE有效方法

    jquery1.9以前 $.browser.msie jquery1.9更高版本 $.browser.msie = /msie/.test(navigator.userAgent.toLowerCas ...

  3. [开源应用]利用HTTPHandler+resumableJs+HTML5实现拖拽上传[大]文件

    前言: 大文件传输一直是技术上的一大难点.文件过大时,一些性提交所有的内容进内存是不现实的.大文件带来问题还有是否支持断点传输和多文件同时传输. 本文以resumableJs为例,介绍了如何在ASP. ...

  4. Linux 系统Telnet服务

    Linux 系统Telnet服务 telnet与ssh相比,安全性能并不高,但是在ssh版本升级或者其他的情况下还是需要开启这一项服务.linux提供服务是由运行在后台的守护进程daemon来执行的, ...

  5. java线程图

  6. nodejs笔记三--url处理、Query String;

    URL--该模块包含用以 URL 解析的实用函数. 使用 require('url') 来调用该模块. 一.parse函数的基础用法 parse函数的作用是解析url,返回一个json格式的数组,请看 ...

  7. CSS3 filter10种特效整理

    -webkit-filter是css3的一个属性,Webkit率先支持了这几个功能,感觉效果很不错.一共有10种最基本的特效,下来这个DEMO很好的展示了这些效果: <!DOCTYPE html ...

  8. javascript 对象数组排序

    参考地址:http://blog.csdn.net/kavensu/article/details/17851329

  9. 我教女朋友学编程Html系列(6)—Html常用表单控件

    做过网页的人都知道,html表单控件十分重要.基本上我们注册会员.登录用户,都需要填写用户名.密码,那些框框都是表单控件. 本来今天就想写一些常用的html表单控件,于是开始搜资料,找到了一个网页,作 ...

  10. proxy server 代理服务器

    有时候,我觉得自己需要去搞明白.搞清楚一个概念,帮我打通一下自己的知识体系,或者说,尝试联络起来. 1. 简介 突破自身IP限制,访问国外站点. 访问单位或者团体内部资源. 突破中国电信的IP封锁. ...