Custom Marker keeps flickering on every render
See original GitHub issueI’m trying to set up a slider with a custom marker that moves with a an updating value. But every time a render is called the Custom marker flickers and makes it hard to grab. If I remove the custom marker the standard marker works perfectly, no flickering and easy to grab.
Here is my slider:
<Multislider
customMarker={() => <Image source={scrubber}/>}
sliderLength={Dimensions.get('window').width - 40}
touchDimensions={{width: 50, height: 50}}
values={[Math.round(slowRacer.currentIndex || 0)]}/>
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
React native map markers flicker on state update
When I update the state in onPress method of the marker all the markers flickers, probably due to re-rendering. I've added the unique...
Read more >Markers | Maps SDK for iOS - Google Developers
Some devices may struggle to render the map if you have many markers on screen, and each marker has its own UIView ,...
Read more >Performant Custom Map Markers for React-Native-Maps
Every time the map updates all of the custom markers are rendered which is quite inefficient as marker pins typically don't change (image...
Read more >Fix export issues in Premiere Pro - Adobe Support
... "Error while compiling" error message when rendering or exporting. ... Check if your System Compatibility Report is throwing any errors.
Read more >Slow rendering - Android Developers
Systrace shows when each frame is drawn and color codes each frame to ... They both contain Systrace markers, so you can use...
Read more >
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 Free
Top 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
@RyanMitchellWilson you can fix this problem witg separate markers in new update.
I am having the exact same issue…is there a workaround??