[ghemical-devel] Constraint View Patch

[Donald Ephraim Curtis]

On Fri, 2006-03-31 at 02:15 -0600, Donald Ephraim Curtis wrote:
> > You should also call model::SystemWasModified() if constraints are added, 
> > removed or modified. I think this will solve the problem you found. When 
> > you set the constraint "disabled", the change was saved into the model 
> > object but it was not passed to the engine object, nor the engine object 
> > was invalidated ; therefore the change did not affect anything in the 
> > calculations and the bond length did not go back to normal.
> 
> I checkedthis out, it's getting called when you update the values of a
> constraint but the constraint isn't getting changed in the engine.  I
> don' know what the deal is.  To reproduce: constrain a bond to 1nm, then
> remove he constraint, it doesn't go back to normal.

sorry, the problem is if you set the min to 1nm (only using minimum)
then change it to .1nm (still using min only) then i doesn't
re-constrain.  does that make sense?  I guess what i am looking for is
that if i do a min constraint very large, then shrink the min constraint
down, it should go to the smaller one i specify, thats not the case.  if
that is the way you want it implemented i think we'll have to live with
it.