[vtk-developers] Issue with Modifieds in vtkInformation*Key

[David Cole]

Go for it. That's a nightmare waiting to happen unless I'm totally missing
the boat on something...

Modified should only be called if something *actually was modified*.


Thanks,
David


On Thu, Jul 10, 2008 at 5:40 PM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

> I have discovered that just about every time you call vtkInformation::Set,
> the vtkInformation object is Modified even when the actual value of the key
> stays the same.  That should not be the case, should it?  All of the vtkSet*
> macros avoid calling Modified if the value does not really change.  The
> problem is that I see in ParaView there are several instances of observes
> attached to information objects designed to push updated values from client
> to server.
>
> Does anyone object to me changing the vtkInformation*Key::Set methods to
> suppress calling Modified when the value remains the same?
>
> -Ken
>
>   ****      Kenneth Moreland
>    ***      Sandia National Laboratories
> ***********
> *** *** ***  email: kmorel at sandia.gov
> **  ***  **  phone: (505) 844-8919
>    ***      fax:   (505) 845-0833
>
>
> _______________________________________________
> vtk-developers mailing list
> vtk-developers at vtk.org
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20080710/d3f4b8f6/attachment.html>