On Thu, Nov 18, 2010 at 11:38:19AM +0000, Garth N. Wells wrote: > > > On 18/11/10 10:56, [email protected] wrote: > >------------------------------------------------------------ > >revno: 5293 > >committer: Anders Logg<[email protected]> > >branch nick: dolfin > >timestamp: Thu 2010-11-18 11:53:44 +0100 > >message: > > Move implementation of coloring data extraction to MeshColoring and > > handle constness. Handles similarly to init functions. > > I'm not too keen on this - the coloring of a const Mesh can be > changed from vertex to edge, for example, despite it being const.
It should still work. The coloring will then be overwritten. I don't see another easy solution. We would then need to color the mesh before sending it to the assembler, which would require the user to do so. What we do know is very similar to the what we do in the init functions. If the assembler needs edges, it will generate them, and if the assembler needs colors, it will generate those too. -- Anders _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : [email protected] Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
