On Wed, Aug 31, 2011 at 03:16:23PM -0700, Johan Hake wrote: > Disclaimer: I have no clue of what you are doing :)
:-) I'm trying to get boundary indicators working again (in parallel). In the process, I'm making some changes and extensions that were suggested (not using MeshData as primary storage). The changes involve the addition of two new classes: MeshDomains and MeshMarkers (used internally by MeshDomains but also useful in itself). Will describe this all in more detail once it's working. > If you want to expose 'set' to Python you rather choose another name... > > set_one, set_value? I suspected as much but couldn't figure out why. So why? The important point is not the set function but the set_marker function that needs to exist in both MeshFunction and MeshMarkers to get a template function to run with both so we avoid reimplementation of that function. Then it felt natural to add a set function as well. -- Anders > Johan > > On Wednesday August 31 2011 14:02:14 nore...@launchpad.net wrote: > > ------------------------------------------------------------ > > revno: 6153 > > committer: Anders Logg <l...@simula.no> > > branch nick: work > > timestamp: Wed 2011-08-31 23:00:04 +0200 > > message: > > Add set_marker function to both MeshFunction and MeshMarkers to make > > templated application of markers in SubDomains work with both. > > modified: > > dolfin/mesh/MeshFunction.h > > dolfin/mesh/MeshMarkers.h > > dolfin/mesh/SubDomain.cpp > > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~dolfin > Post to : dolfin@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dolfin > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : dolfin@lists.launchpad.net Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
