Actually, after looking at the amount of work required for a change nobody is going to use, I'm just going to skip it. PointLocatorList already breaks unless your mesh is the Voronoi diagram of the elements' centroids and you have a fetish for using O(N) instead of O(NlogN) algorithms; if any such user exists, asking that the mesh be serial as well probably isn't going to be the straw that breaks the camel's back.
Never mind... --- Roy On Thu, 18 Feb 2010, Roy Stogner wrote: > From now on, operator(Point &p) will search for an active element > containing p, not just the element nearest p, and if it doesn't find a > containing active element it will just return NULL. This is to make > it more consistent with PointLocatorTree, and to make it useful on > ParallelMesh. > > This is a major behavior change, so I feel compelled to mention it on > the lists, but it's also a behavior change in code nobody uses or > should use, so I won't have trouble sleeping tonight. > --- > Roy > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
