yade-users team mailing list archive

[Václav Šmilauer <eudoxos@xxxxxxxx>]

> In previous versions, you could switch on/off automatic deletion 
> handling inside the collider (even before, there was no switch and the 
> collider was _always_ erasing distant interactions). It could be set 
> back that way probably, but it doesn't really change the problem : the 
> user has to keep in mind to put "requestErase" in his law, in one case, 
> OR he has to remember to set collider->eraseDistant =true in his 
> simulation in the other case.

eraseDistant is not going to happen again, the framework should be
general enough so that all colliders can behave the same. The rule is: 

* collider creates and deletes potential interactions
* Ig2 functors perform the potential->real transition (return status of Ig2::go)
* Law2 functors does the real->potential transition via requestErase.

Note: there is no real->nothing transition; OTOH nothing->real can be
triggered by hand.

Cheers, v.