onClick on overlapping areas triggers all, even with different z

[pjoe]

Using kaboom 3000.0.3.

Expect: onClick only to trigger on topmost GameObj if there are overlapping areas, especially if they have different z

Actual: All onClick handlers matching mousepos are triggered

Example: https://replit.com/@pjoePanda/kaboom3000-area-click-overlap

[pjoe]

FWIW: doing this as work around:

  onClick(() => {
    const pos = mousePos();
    const match = get("tile").reduceRight<GameObj | undefined>((acc, go) => {
      if (acc && acc.z >= go.z) return acc;
      if (go.hasPoint(pos)) return go;
      return acc;
    }, undefined);
    if (match) {
      console.debug(`match id:${match.id}, type:${match.tileType}`);
      match.destroy();
    }
  });

[slmjkdbtl]

This is the expected behavior, you can check this example which iterates objects in reverse z order to check for mouse click

[pjoe]

Can then simplify to:

  onClick(() => {
    const clicked = get("tile").findLast((go) => go.isHovering());
    if (clicked) {
      clicked.destroy();
    }
  });

[pjoe]

Looks like z sorting already happens in update: https://github.com/replit/kaboom/blob/master/src/kaboom.ts#L3026

[slmjkdbtl]

Yep z sorting is done when updating / drawing objects, but not in get()

[pjoe]

Ok, however the sort inside update is "inplace" as far as I can see, so it persists after the the update. At least for my use case this is good enough as I'm not rapidly adding new objects and calling get between updates.

[slmjkdbtl]

Oh yes you are right, it does persist every frame