On Thu, 2 Dec 2010, Boyce Griffith wrote: > Looking around, there are some other places in libMesh that appear not to > handle multiple boundary IDs per side. In particular: > > fe_base.C ~ around line 2018 > mesh_communication.C ~ around lines 364 and 1080 > mesh_modification.C ~ around lines 840, 1224 and 1292 > unstructured_mesh.C ~ around line 914 > > I think that in each case, it should suffice to loop over the IDs returned by > BoundaryInfo::boundary_ids().
Looks right on first glance. > If you agree, I'm happy to send a patch. Thanks! That would be great. Would you attach it as a separate file next time, though? Last patch seemed to have been mangled just enough by email reformatting that it didn't apply cleanly. --- Roy ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
