Ivan Volynkin

I've found out very interesting solution! ``` @Override public boolean onTouch(View v, MotionEvent event) { + if (isZoomed()) + image.getParent().requestDisallowInterceptTouchEvent(true); ``` ``` + private boolean zoomed; + public boolean isZoomed()...

Not `Handler` exactly, it may be any main-thread executor. But, Android's `View` class uses `Handler` to schedule `Drawable`'s tasks. Unfortunately, Android's `Handler` doesn't implements Java's abstract interface `java.util.concurrent.Executor`.

If `Drawable` wants to schedule some task, it can use it's `Callback`. But if this `Callback` has `MultiCallback` implementation, the task will be executed by each of the members of...

You can implement both of these: single executor and executors from `Callback` members.

I have the same issue. I noticed some peer's ports are changed randomly when "could not decrypt message" error appears. Command `netclient pull` restores connection.