Skip to main content
Point data is typically cached on the native side. On the RN side, you fetch data on demand via an accessor. ElementDataAccessor also keeps a smaller cache of its own on the RN side: read methods such as get/getRange cache the values they fetch to avoid repeated cross-boundary reads, while write methods such as add/set/setRange clear that cache on success so subsequent reads see the latest data. This RN-side cache is separate from the native-side Element cache described in Element Caching and Release: releasing a whole Element (recycleElement/clearElementCache) also clears the accessor-level cache underneath it, but calling an accessor’s own clearCache() does not affect the native-side Element cache.
If you know in advance that you’ll read a contiguous range of point data (e.g. rendering a stroke segment), call preload(startIndex, count) first to warm the cache, then read with get/getRange to reduce the number of cross-boundary calls.

ElementPointDataType

Point data types exposed by ElementDataAccessor (enum).