You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In most cases, the user will pass one value per geometry, and then the layer will handle expanding that value to be per-vertex (arrow.Vector<arrow.Float> for example). But the layer should also allow a per-vertex input (i.e. arrow.Vector<arrow.List<arrow.Float>>). Then the user has total control over the per-vertex styling.
The layer should validate that the array offsets are the same for the passed-in vector as for the geometry offsets.
The text was updated successfully, but these errors were encountered:
In most cases, the user will pass one value per geometry, and then the layer will handle expanding that value to be per-vertex (
arrow.Vector<arrow.Float>
for example). But the layer should also allow a per-vertex input (i.e.arrow.Vector<arrow.List<arrow.Float>>
). Then the user has total control over the per-vertex styling.The layer should validate that the array offsets are the same for the passed-in vector as for the geometry offsets.
The text was updated successfully, but these errors were encountered: