P.S. I meant to say that I'd be happy to make a PR with that fix, but I
wasn't sure what the best way to fix this is. Inside MeshFunction::clone()
we could check if the original MeshFunction is initialized and if it is
then initialize the clone? That seems reasonable to me.
David
On Wed, May 25, 2016 at 11:20 PM, David Knezevic <david.kneze...@akselos.com
> wrote:
> I tried to do System::project_solution based on a MeshFunction, and I hit
> an assertion failure indicating that the MeshFunction was not initialized.
> I believe the issue is that project_solution creates a WrappedFunctor based
> on the *clone* of the MeshFunction, and the clone is not initialized.
>
> I verified that adding a call to MeshFunction::init inside
> MeshFunction::clone (so that the clone gets initialized) fixes this issue.
>
> David
>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
