teaching machines

SENG 440: Lecture 20 – Multitouch

May 16, 2019 by . Filed under lectures, semester1-2019, seng440.

Dear students,

Today we write an app that solves the problem of choosing of which player goes first in a game. All players place a finger on the phone, and the app chooses one of them randomly. The game is inspired by the commercial app Chwazi.

Next lecture we will discuss writing an app that is multitouch-aware. See the TODO below for the assigned exercises.


Following are the exercises assigned last time. We will use and discuss the solutions that you’ve submitted as we assemble our app, but I include my solutions here for reference.

  1. Declare a PreferenceScreen resource in xml/preferences.xml to present a single EditText preference for the delay in seconds from the last down or up event until one of the active pointers is randomly picked. Make the preference a decimal number with key pickDelay. Give it a title, a summary, a default of 3, and an icon of @drawable/timer. Possible solution.
    <PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android">
        android:summary="Time in seconds until random player selected"
        android:title="Delay" />
  2. Define class SettingsFragment as a subclass of PreferenceFragmentCompat that shows the app’s PreferenceScreen. Possible solution.
    class SettingsFragment : PreferenceFragmentCompat() {
      override fun onCreatePreferences(savedInstanceState: Bundle?, rootKey: String?) {
        setPreferencesFromResource(R.xml.preferences, rootKey)
        findPreference<EditTextPreference>("delayToPick")?.let {
          it.setOnBindEditTextListener { editor ->
            editor.inputType = InputType.TYPE_CLASS_NUMBER
  3. Define field pickTask in PickerView to be a Runnable that sets pickedId to a randomly chosen key from pointerIdToPosition. Also, declare field onFirstDown in PickerView to be a lambda that accepts no parameters and returns nothing. Define it to do nothing, but allow clients to redefine it to trigger some action when a first touch event occurs. Possible solution.
    private val pickTask = Runnable {
      pickedId = pointerIdToPosition.keys.random()
  4. Write method schedulePick that invalidates pickedId and unschedules pickTask from the inherited handler. If there are any entries left in the positions map, schedule pickTask to execute after the pick delay, which you can access via prefs. Watch your units. Possible solution.
    private fun schedulePick() {
      pickedId = -1
      if (pointerIdToPosition.isNotEmpty()) {
        val delay = ((prefs.getString("pickDelay", null) ?: "3").toFloat() * 1000).toLong()
        handler.postDelayed(pickTask, delay)
  5. Write method handleDowns in PickerView to accept a MotionEvent parameter. Call onFirstDown when the first touch occurs. When any down event occurs, first or otherwise, do two things:
    • Reschedule the picking.
    • Map the active pointer to position (0, 0)—but only if the map doesn’t already have an entry for the pointer.
    Possible solution.
    private fun handleDowns(event: MotionEvent) {
      if (event.actionMasked == MotionEvent.ACTION_DOWN) {
      when (event.actionMasked) {
        MotionEvent.ACTION_POINTER_DOWN -> {
          val id = event.getPointerId(event.actionIndex)
          if (!pointerIdToPosition.containsKey(id)) {
            pointerIdToPosition[id] = PointF()
  6. Write method handlePositions in PickerView to accept a MotionEvent parameter. Iterate through all the currently tracked pointers and update the positions map. Possible solution.
    private fun handlePositions(event: MotionEvent) {
      repeat (event.pointerCount) { i ->
        id = event.getPointerId(i)
        pointerIdToPosition[id]?.apply {
          x = event.getX(i)
          y = event.getY(i)
  7. Write method handleUps in PickerView to accept a MotionEvent parameter. When any up event occurs, first or otherwise, do two things:
    • Reschedule the picking.
    • Remove any entry for the active pointer from the positions map.
    Possible solution.
    private fun handleUps(event: MotionEvent) {
      when (event.actionMasked) {
        MotionEvent.ACTION_UP, MotionEvent.ACTION_POINTER_UP -> {
  8. Write method onTouchEvent in PickerView to handle any down events, update the tracked pointer positions, and handle any update events. Also, so that the UI reflects the pointer state, force the view to be redrawn. Possible solution.
    override fun onTouchEvent(event: MotionEvent): Boolean {
      return true
  9. Write method drawFingerprint in PickerView to accept a Canvas parameter. Draw fingerprint in the center of the view, ensuring that it fits within the bounds. Assume that the fingerprint is square. Possible solution.
    private fun drawFingerprint(canvas: Canvas) {
      val imageAspect = fingerprint.intrinsicWidth / fingerprint.intrinsicHeight.toFloat()
      val frameAspect = width / height.toFloat()
      val boxWidth: Int
      val boxHeight: Int
      if (frameAspect < imageAspect) {
        boxWidth = width
        boxHeight = (width / imageAspect).toInt()
      } else {
        boxHeight = height
        boxWidth = (height * imageAspect).toInt()
      val centerX = (width * 0.5f).toInt()
      val centerY = (height * 0.5f).toInt()
      fingerprint.setBounds(centerX - boxWidth / 2, centerY - boxHeight / 2, centerX + boxWidth / 2, centerY + boxHeight / 2)
  10. Write method onDraw in PickerView to accept a Canvas parameter. If there are no currently tracked pointers, draw the fingerprint as a cue for the user to press the screen. Otherwise, draw circles around each pointer. Use unpickedPaint by default, but if a pointer is the picked pointer, use pickedPaint. Possible solution.
    override fun onDraw(canvas: Canvas) {
      if (pointerIdToPosition.isEmpty()) {
      } else {
        pointerIdToPosition.forEach { id, p ->
          canvas.drawCircle(p.x, p.y, 150f, if (id == pickedId) pickedPaint else unpickedPaint)
  11. Write method enableFullscreen in MainActivity to put the app into fullscreen immersive mode. Ensure that a stable layout is used—even when the navigation controls and status bar are visible. Possible solution.
    private fun enableFullscreen() {
      window.decorView.systemUiVisibility =


Next lecture we will examine two common gestures that occur on mobile platforms: pinch-and-zoom and panning. We won’t create a full app, just a custom view that displays an image and supports these two gestures. Here’s the start to the custom view:

class ZoomPanView @JvmOverloads constructor(context: Context, attributes: AttributeSet? = null, styleAttributes: Int = 0) : View(context, attributes, styleAttributes) {
  private val image: Bitmap = BitmapFactory.decodeResource(resources, R.drawable.some_image)
  private var bounds = RectF()

The image will be drawn in the view’s Canvas inside the frame demarcated by bounds. Most of the exercises deal with adjusting bounds appropriately.

The main activity does nothing but load this layout:

<org.twodee.zoompan.ZoomPanView xmlns:android="http://schemas.android.com/apk/res/android"
  tools:context=".MainActivity" />

The exercises that you will collectively complete are listed below. Check your email for your assigned exercise and a link to submit your solution. Become an expert on your particular corner of the app, investigating background material as needed. Build on top of the activity and others’ code as you complete your exercise. No solution should be very long, but some have more overhead like curly braces and method signatures than others.

  1. Define field panListener to be a SimpleOnGestureListener. When a scroll event happens, it shifts the bounding box by the scrolled distance and forces the view to be redrawn.
  2. Define field zoomListener to be a SimpleOnScaleGestureListener. When a scale event happens, scale the bounding box. Bonus points if you clamp the scale from becoming too small. Tall poppy points if you scale about fingers’ centroid rather than (0, 0).
  3. Investigate gesture detectors in Android. Define fields panDetector and zoomDetector to be detectors for the two listeners defined in the previous steps.
  4. Define method fillWidth to set the bounds such that the image fills the view’s width. Set the height to maintain the image’s aspect ratio.
  5. Define method fillHeight to set the bounds such that the image fills the view’s height. Set the width to maintain the image’s aspect ratio.
  6. Define method onSizeChanged to set the bounds to fill the view as much possible—filling either the width or height. Bonus points if you figure out what criteria can fit the image to the view without cropping any of it.
  7. Define method onDraw to draw the bitmap to fill the current bounds.
  8. Define method onTouchEvent to let the detectors process the event.

See you next time!


P.S. It’s time for a haiku!

It’s not multitouch
When I flit across the phone
It’s finger skating


Leave a Reply

Your email address will not be published. Required fields are marked *