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
I'm looking at the code for Heightmap, trying to see how this would be with a different kind of heightmap (that is put on top of a cylinder instead of a plane).
I see that PersistentQueryDispatcher::contact_manifolds simply goes through contact_manifolds_heightfield_shape and contact_manifolds_heightfield_composite_shape for heightfields. These methods seem general enough.
Would it be reasonable to expose them behind a trait? Just like as_support_map exposes a generic interface trait SupportMap, can we have as_heightmap exposing some trait Heightmap?
The text was updated successfully, but these errors were encountered:
Branching off from #773
I'm looking at the code for
Heightmap
, trying to see how this would be with a different kind of heightmap (that is put on top of a cylinder instead of a plane).I see that
PersistentQueryDispatcher::contact_manifolds
simply goes throughcontact_manifolds_heightfield_shape
andcontact_manifolds_heightfield_composite_shape
for heightfields. These methods seem general enough.Would it be reasonable to expose them behind a trait? Just like
as_support_map
exposes a generic interfacetrait SupportMap
, can we haveas_heightmap
exposing sometrait Heightmap
?The text was updated successfully, but these errors were encountered: