On Tue, 15 Sep 2009, Roy Stogner wrote:
> Here's a thought: Derek's change counter suggestion is probably > misleading in MeshBase, but it might be suited for MeshRefinement. > That would make it clearer that the counter was just tracking > refinement/coarsening changes, and not anything like mesh movement. > On the other hand, people often create and destroy MeshRefinement > objects willy-nilly since they don't currently store any state beyond > refinement heuristic parameters; it would be a pretty easy application > bug to trust a change count that was getting deleted after and reset > before each refinement step. Oh, and of course the MeshRefinement object(s) would be living in user code, where at least some of the code Derek is interested in (like the exodus IO) wouldn't be able to get a handle on them. Never mind. --- Roy ------------------------------------------------------------------------------ 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
