On Sep 15, 2009, at 1:02 PM, John Peterson wrote: > I see. What if MeshRefinement stored the result of its most recent > refine/coarsen_elements call? > > If not in MeshRefinement, then anywhere all these different pieces > have access to should be sufficient... maybe even a global variable ;)
Just storing the bool isn't enough.... who turns it back to false? What if you only refine once and that bool gets set to true... from then on everything will think the mesh is always changing. That's the reason I suggested a count. Because each piece of code that is interested in whether or not the mesh has changed can store the number of changes and compare that in the future to decide if the mesh has changed since the last time that code was called... Derek ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
