FAQ
“Unresolved reference: Path”
Section titled ““Unresolved reference: Path””Kotlin’s standard library has kotlin.io.path.Path. Use an import alias:
import io.github.jayteealao.isometric.Path as IsoPath“Color is ambiguous”
Section titled ““Color is ambiguous””Compose has androidx.compose.ui.graphics.Color. The library uses IsoColor:
import io.github.jayteealao.isometric.IsoColor// Use IsoColor(r, g, b) everywhere in isometric scenesConvert between them: composeColor.toIsoColor() / isoColor.toComposeColor()
”Shapes render in wrong order”
Section titled “”Shapes render in wrong order””Isometric uses depth sorting: depth = x + y - 2z. Shapes with higher depth render on top. If shapes overlap incorrectly:
- Check that
RenderOptions.enableDepthSortingis true (default) - Adjust positions so overlapping shapes have clearly different depths
- Known limitation: the Knot shape has depth-sorting issues with its internal faces
”Scene is blank / nothing renders”
Section titled “”Scene is blank / nothing renders””- Ensure
IsometricSceneis in a Compose context - Check shape positions — shapes at very large coordinates may be off-screen
- Verify colors have non-zero alpha (default is 255)
- Make sure the
IsometricScenehas non-zero size (useModifier.fillMaxSize())
“Is this published to Maven Central?”
Section titled ““Is this published to Maven Central?””Yes. All three modules are published to Maven Central. See the Installation guide for coordinates and version catalog setup.
”Can I use this without Compose?”
Section titled “”Can I use this without Compose?””Yes. The isometric-core module is pure Kotlin/JVM with no Android dependency. Use IsometricEngine directly to project shapes to 2D coordinates, then render with your own backend.
”How do I use the old View API?”
Section titled “”How do I use the old View API?””The isometric-android-view module provides IsometricView for the traditional Android View system. See the Migration guide for details on moving to Compose.