@riggaroo Great to see this out there!
Is there a new createChainEffect API that's different from the original one released in Android 12
https://t.co/KT8tbHkOIq?
@MatejKnopp@JimSproch@alexmercerind @mickrich384 @mahersafadii As @JimSproch had mentioned, Compose on Android leverages the same rendering primitives as the View system. That is both Compostables and Views all draw with the same https://t.co/wjhRnAttgU.Canvas instance. It's no different than any other custom Android View in this regard
@Alex_Zhukovich@ComposeBot While you can use the alpha modifier here, it would be preferable to use colors with alpha baked in as it avoids the overhead of rendering into an offscreen buffer.
@BreensR You can use Modifier.paint and pass a Painter to draw an image within any composable. The Image composable implementation does this internally.
@zachklipp Yes as @romainguy mentioned this maybe a discrepancy between 3x3 and 4x4 matrices. Need to verify, but the 3x3 matrix requirement maybe actually enforced elsewhere but may not be applied to later transformations.
@mzmzgreen@JimSproch@Zhuinden We designed a number of the graphics facilities with interfaces in order to support desktop as well as Android. However, you may end up having to make some trade offs as a result (ex, not supporting existing Android views).
@JimSproch@Zhuinden Additionally the shadow approach used for MaterialShapeDrawable is sufficient for some path shapes (like rounded rects) but might not scale appropriately to any generic shape.
@JimSproch@Zhuinden Also we do not recommend using Paint#setShadowLayer as it only works on software enabled Canvas objects until relatively recently.
While it is possible to recreate some shadow effects using paths and gradients, paths are purely CPU rendered.