创建一个message并赋值obj参数,然后携带message调用了sendMessage方法
new Thread(() -> {
Message message = Message.obtain();
message.obj = “好好学习”;
mHandler.sendMessage(message);
}).start();
**Handler#sendMessage**
sendMessage调用了sendMessageDelayed
public final boolean sendMessage(@NonNull Message msg) {
return sendMessageDelayed(msg, 0);
}
**Handler#sendMessageDelayed**
sendMessageDelayed调用了sendMessageAtTime
public final boolean sendMessageDelayed(@NonNull Message msg, long delayMillis) {
if (delayMillis < 0) {
delayMillis = 0;
}
return sendMessageAtTime(msg, SystemClock.uptimeMillis() + delayMillis);
}
**Handler#sendMessageAtTime**
sendMessageAtTime调用了enqueueMessage,这里出现了mQueue,也就是消息队列,暂时不用管,下面会解释。
public boolean sendMessageAtTime(@NonNull 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);
}
**Handler#enqueueMessage**
enqueueMessage调用了queue.enqueueMessage(),并把message传了进去
private boolean enqueueMessage(@NonNull MessageQueue queue, @NonNull Message msg,
long uptimeMillis) {
msg.target = this;
msg.workSourceUid = ThreadLocalWorkSource.getUid();
if (mAsynchronous) {
msg.setAsynchronous(true);
}
return queue.enqueueMessage(msg, uptimeMillis);
}
上面流程走完,大家是不是很懵逼,mQueue消息队列是啥玩意? mQueue初次相遇
应该是sendMessageAtTime方法:
public boolean sendMessageAtTime(@NonNull Message msg, long uptimeMillis) {
MessageQueue queue = mQueue;
…
return enqueueMessage(queue, msg, uptimeMillis);
}
看起来是个成员变量,我们去成员变量找一下:
public class Handler {
…
final MessageQueue mQueue;
…
}
找找在哪里赋值的:
public Handler(@Nullable Callback callback, boolean async) {
…
mLooper = Looper.myLooper();
…
mQueue = mLooper.mQueue;
mCallback = callback;
mAsynchronous = async;
}
原来是在两个参数的构造方法中被赋值了,调用Looper.myLooper() 拿到mLooper,然后调用mLooper.mQueue方法,也就是说mQueue是Looper的一个成员变量。
以我们目前分析的源码,只知道我们把Message放入了MessageQueue中:
Looper初次相遇
是在Handler两个参数的构造方法中,但是Looper并不是在这里创建的,那在哪里创建的呢?一切还要从盘古开天地说起:
在我们的程序启动后,经过一系列的启动流程,最终将会调用我们的ActivityThread.java这个类,这个类里面有个main()方法,这个main方法大家一定不会陌生:
**ActivityThread#main**
ActivityThread的main()首先调用了Looper.prepareMainLooper,初始化了Looper
public static void main(String[] args) {
…
Looper.prepareMainLooper();
…
Looper.loop();
}
**Looper#prepareMainLooper**
调用了prepare并传入了false
public static void prepareMainLooper() {
prepare(false);
synchronized (Looper.class) {
if (sMainLooper != null) {
throw new IllegalStateException(“The main Looper has already been prepared.”);
}
sMainLooper = myLooper();
}
}
**Looper#prepare**
这里new了一个Looper,然后放进了ThreadLocal里面
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构造方法中初始化了一个MessageQueue
private Looper(boolean quitAllowed) {
mQueue = new MessageQueue(quitAllowed);
mThread = Thread.currentThread();
}
- ThreadLocal是什么?
ThreadLocal源码还是比较复杂的,所以我会专门写一篇文章来讲解,大家暂时理解为: 同一个ThreadLocal在不同的线程中set和get可以实现数据隔离,线程之间互不影响。比如A线程存入一个1,B线程存储一个2,那在A线程中获取的值是1,B线程获取的值是2
public class HelloThreadLocal {
public static void main(String[] args) {
ThreadLocal threadLocal = new ThreadLocal<>();
new Thread(() -> {
threadLocal.set(1);
System.out.println(Thread.currentThread().getName()+": "+threadLocal.get());
},“线程A”).start();
new Thread(() -> {
threadLocal.set(2);
System.out.println(Thread.currentThread().getName()+": "+threadLocal.get());
},“线程B”).start();
}
}
执行结果:
线程A: 1
线程B: 2
**回到Looper#prepare**
现在我们学会了ThreadLocal,再来看一遍这个代码,这里有一个判断,如果ThreadLocal获取的值不为空,就会抛出异常,否则就存储一个Looper到当前线程,这里用了ThreadLocal的特性,可以保证我们一个线程最多只有一个Looper。
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));
}
**回到ActivityThread#main**
上面我们已经分析完了Looper.prepareMainLooper(),会创建一个Looper对象存到ThreadLocal,现在我们看到main()还执行了Looper.loop()方法。
public static void main(String[] args)
{
…
Looper.prepareMainLooper();
…
Looper.loop();
}
**Looper#loop**
loop方法中的代码特别多,这里我们精简之后大概还剩这么多代码:
-
通过myLooper()从ThreadLocal中拿到我们存放的Looper对象me
-
从me中拿到Looper的消息队列queue
-
创建一个死循环不停地从queue消息队列中取数据
-
如果数据为null就直接return,如果有数据就调用Handler的dispatchMessage方法
public static void loop() {
final Looper me = myLooper();
…
final MessageQueue queue = me.mQueue;
…
for (;😉 {
Message msg = queue.next();
if (msg == null) {
return;
}
…
msg.target.dispatchMessage(msg); //如果消息不等于null,就会走这里
}
…
}
**Handler#dispatchMessage**
如果消息队列循环不等于null,就会走这个方法,然后调用handleMessage(msg)
public void dispatchMessage(@NonNull Message msg) {
if (msg.callback != null) {
handleCallback(msg);
} else {
if (mCallback != null) {
if (mCallback.handleMessage(msg)) {
return;
}
}
handleMessage(msg);
}
}
**Handler#handleMessage**
这个方法是一个空实现,最终由用户定义的Handler子类实现。
public void handleMessage(@NonNull Message msg) {
}
**自己的定义的Handler#handleMessage**
会回调到我们自己的Handler的handleMessage方法,并传回Message
private Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
super.handleMessage(msg);
Log.d(“lkx”, (String) msg.obj);