Fixed in r4982
** Changed in: yade
Status: New => Fix Released
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1476159
Title:
several ForceContainer.addF behaves non-intuitively with
permanent=True
Status in Yade:
Fix Released
Bug description:
Hi all,
consider
O.forces.addF(id,(2,0,0),True)
... # some code, a few steps or whatever
O.forces.addF(id,(4,0,0),True)
what should be the result? Intuitively (according to addF name), I
would expect applied force (6,0,0). However, the permanent force is
rewritten with (4,0,0), so applied force (4,0,0) is the result..
I suggest to split addF to 2 cases:
1) addF without permanent parameter
2) setPermanentForce ()or something similar), substituting
addF(permanent=True), with the name reflecting more accurately what it really
does..
any suggestions or comments?
cheers
Jan
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1476159/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~yade-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
