ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to spot empty or inverted Rect objects that break hit‑testing, drawing, or layout, and follow a step‑by‑step guide to verify, fix, and escalate the problem.
Integration boundary I am designing a screen where a legacy View hierarchy (containing its own touch handling, e.g. a custom map or drawing surface) is embedded in Jetpack Compose via AndroidView , and the surrounding Compose tree also uses pointerInput modifiers for gestures. Goal and constraints The goal is predictable, deterministic touch dispatch: I need
Background Swiper supports nested carousels via the nested option. When both parent and child Swipers have allowTouchMove enabled, the library’s event delegation may let the child consume a swipe, but the parent can still register a touchstart and trigger a slide change. Uncertainty The current documentation does not specify whether the parent automatically
android
rect
jetpackcompose
swiper