Using .value vs .current for Skia Values
#1059
elliotwaite
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I read in this discussion that you're working on adding support for UI thread rendering. This seems like it will open the door to React Native Skia interoperating well with Reanimated and React Native Gesture Handler. Since those libraries both use Shared Values, which are accessed and assigned to using the
.valueproperty, I was wondering if it might be more intuitive if users could also access and assign to Skia Values using the.valueproperty as well.I know that React refs use the
.currentproperty, but from my experience with using Shared Values, I've grown used to using their.valueproperty, and it currently feels a bit odd to use.currentwhen accessing Skia Values since I think about them similarly to how I think about Shared Values.So I was wondering what the React Native Skia team's thoughts were on using
.currentvs.value. I understand that switching to.valueat this point might be too disruptive of a change, but since React Native Skia is still in the alpha stage, I thought this topic might still be worth exploring.Beta Was this translation helpful? Give feedback.
All reactions