Using clockRunning/stop/start clock inside the proc
See original GitHub issueI’ve been playing with proc
and it looks so promising!
But I’ve noticed it doesn’t work with clockRunning, startClock, stopClock
blocks, since we are passing animated param into each of them and all of this invariants throw.
If I commented those invariants, app crashes on execution. On Android it says something like that:
By the way, here are some perf results with my example. You can change these lines to use different versions. It renders 100 animated views, also animates 4 properties of each one with timing
, so there are 400 timings.
Check out perf monitor and delay until animation plays.
With some atomic proc usage (everything except clockRunning, startClock, stopClock):
Everything wrapped with proc:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:11 (5 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@khorark You can pass the clock as an argument, however, currently, you cannot call
stopClock
,clockRunning
,startClock
inside the proc.Ok