Handler消息机制解析
Handler消息机制解析
Android提供用来更新UI的一套机制,也是一套消息处理机制,可以发送消息和处理消息。
Handler
Handler对象来与Looper沟通,以便push新消息到MessageQueue里;或者接收Looper从Message Queue取出)所送来的消息。
方法
-
构造方法
public Handler(Callback callback, boolean async) { if (FIND_POTENTIAL_LEAKS) { final Class<? extends Handler> klass = getClass(); if ((klass.isAnonymousClass() || klass.isMemberClass() || klass.isLocalClass()) && (klass.getModifiers() & Modifier.STATIC) == 0) { Log.w(TAG, "The following Handler class should be static or leaks might occur: " + klass.getCanonicalName()); } } mLooper = Looper.myLooper(); if (mLooper == null) { throw new RuntimeException( "Can't create handler inside thread that has not called Looper.prepare()"); } mQueue = mLooper.mQueue; mCallback = callback; mAsynchronous = async; }
几个构造方法最终都会调用这个构造方法,myLooper()
。获取当前Looper对象,通过looper获取MessageQueue,完成了handler和looper的关联
-
消息发送方法
public boolean sendMessageAtTime(Message msg, long uptimeMillis) { MessageQueue queue = mQueue; if (queue == null) { RuntimeException e = new RuntimeException( this + " sendMessageAtTime() called with no mQueue"); Log.w("Looper", e.getMessage(), e); return false; } return enqueueMessage(queue, msg, uptimeMillis); }
如果队列为null
就抛异常,否则向队列中放入消息。
private boolean enqueueMessage(MessageQueue queue, Message msg, long uptimeMillis) {
msg.target = this;
if (mAsynchronous) {
msg.setAsynchronous(true);
}
return queue.enqueueMessage(msg, uptimeMillis);
}
放入消息的时候要指定目标,默认是发送个自己。
消息放入队列后,Looper通过looper()
处理消息队列
-
分发消息方法
/** * Handle system messages here. */ public void dispatchMessage(Message msg) { if (msg.callback != null) { handleCallback(msg); } else { if (mCallback != null) { if (mCallback.handleMessage(msg)) { return; } } handleMessage(msg); } }
在这个方法内调用handleCallback
方法处理消息
内部接口Callback
public interface Callback {
public boolean handleMessage(Message msg);
}
Looper
一个线程只能产生一个Looper对象,由它来管理此线程里的MessageQueue(消息队列)。
- 内部包含了一个消息队列
MessageQueue
所有handler发送的消息都通过这个队列。 - Looper.Looper方法是一个死循环,不断从
MessageQueue
中取Message,有就处理,没有就阻塞
Looper类的方法
-
Looper.prepare()方法(调用prepare(true))
private static void prepare(boolean quitAllowed) { if (sThreadLocal.get() != null) { throw new RuntimeException("Only one Looper may be created per thread"); } sThreadLocal.set(new Looper(quitAllowed)); }
这个方法创建新的Looper
,如果一个线程中已经有一个Looper就会报错,如果没有就调用私有构造方法创建一个新的Looper
-
私有的构造方法
private Looper(boolean quitAllowed) { mQueue = new MessageQueue(quitAllowed); mThread = Thread.currentThread(); }
创建了一个MessageQueue
,并关联当前Thread
-
myLopper()
/** * Return the Looper object associated with the current thread. Returns * null if the calling thread is not associated with a Looper. */ public static @Nullable Looper myLooper() { return sThreadLocal.get(); }
获取当前Looper对象,
-
myQueue()
/** * Return the {@link MessageQueue} object associated with the current * thread. This must be called from a thread running a Looper, or a * NullPointerException will be thrown. */ public static @NonNull MessageQueue myQueue() { return myLooper().mQueue; }
获取Looper中的MessageQueue
-
死循环方法 loop()
/** * Run the message queue in this thread. Be sure to call * {@link #quit()} to end the loop. */ public static void loop() { final Looper me = myLooper(); if (me == null) { throw new RuntimeException("No Looper; Looper.prepare() wasn't called on this thread."); } final MessageQueue queue = me.mQueue; // Make sure the identity of this thread is that of the local process, // and keep track of what that identity token actually is. Binder.clearCallingIdentity(); final long ident = Binder.clearCallingIdentity(); for (;;) { Message msg = queue.next(); // might block if (msg == null) { // No message indicates that the message queue is quitting. return; } // This must be in a local variable, in case a UI event sets the logger Printer logging = me.mLogging; if (logging != null) { logging.println(">>>>> Dispatching to " + msg.target + " " + msg.callback + ": " + msg.what); } msg.target.dispatchMessage(msg); if (logging != null) { logging.println("<<<<< Finished to " + msg.target + " " + msg.callback); } // Make sure that during the course of dispatching the // identity of the thread wasn't corrupted. final long newIdent = Binder.clearCallingIdentity(); if (ident != newIdent) { Log.wtf(TAG, "Thread identity changed from 0x" + Long.toHexString(ident) + " to 0x" + Long.toHexString(newIdent) + " while dispatching to " + msg.target.getClass().getName() + " " + msg.callback + " what=" + msg.what); } msg.recycleUnchecked(); } }
这个方法用于处理队列中的消息:通过myLooper()方法获取单前的Looper
,从而获取当前的消息队列,通过消息队列的next()
方法获取消息,消息不为null的时候调用handler的dispatchMessage(msg)
方法
MessageQueue消息队列
存储消息的容器
ThreadLocal class
作用:在线程中保存信息变量。负责thread和looper之间的关系
方法
-
set
public void set(T value) { Thread currentThread = Thread.currentThread(); Values values = values(currentThread); if (values == null) { values = initializeValues(currentThread); } values.put(this, value); }
键值对的形式存储Thread和Looper之间的关系,Thread是key,Looper是值
-
get
public T get() { // Optimized for the fast path. Thread currentThread = Thread.currentThread(); Values values = values(currentThread); if (values != null) { Object[] table = values.table; int index = hash & values.mask; if (this.reference == table[index]) { return (T) table[index + 1]; } } else { values = initializeValues(currentThread); } return (T) values.getAfterMiss(this); }
取出当前线程对应的looper。
内部类 Values
下一篇: Handler传递Bitmap