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
This issue is meant to record everyone's requests/wishes with regard to the capabilities they'd like with regard to the webchurch-box2D integration.
The current state is described here. However, if you'd like a particular feature, specify it here explicitly (in detail and maybe with example scenarios or pseudo-code).
The text was updated successfully, but these errors were encountered:
Joints can be used to specify many different relationships between objects. For my own purposes it would be particularly useful to define for example that two objects need to be 'glued together' (e.g. distance joint) rather than specifying some odd spring-like force to make sure that they do stick together, until such a moment that a force is applied and then they break apart.
The cognitive idea is that children might be a bit over-prolific in assuming contact-joints, which can explain a key part of development of stability notions.
I know porting over all the joint library is probably too much of a head-ache, but as a 'wish-list' item, I thought I'd mention at least the basic joints: distance, weld, maybe pulley.
This issue is meant to record everyone's requests/wishes with regard to the capabilities they'd like with regard to the webchurch-box2D integration.
The current state is described here. However, if you'd like a particular feature, specify it here explicitly (in detail and maybe with example scenarios or pseudo-code).
The text was updated successfully, but these errors were encountered: