I think the issue is that it sets it back to the old value of skip_renumber
at the end of prepare_for_use(). This is only an issue in parallel...
where I believe the renumbering can actually happen and multiple spots. So
basically, even though we're passing "true" to skip renumbering... that's
only being used during prepare_for_use() and then forgotten after that
point... which wasn't what the old behavior did.
Derek
On Thu, Oct 25, 2012 at 10:07 AM, Roy Stogner <royst...@ices.utexas.edu>wrote:
>
> On Thu, 25 Oct 2012, Derek Gaston wrote:
>
> Hmmm - something is kind of weird here. It looks like you've left
>> in the prepare_for_use() argument to skip_renumber... but it doesn't
>> work. If I call prepare_for_use(true) I get renumbering.
>>
>
> I'm baffled... If skip_renumber_nodes_and_**elements is passed in as
> true, then
>
> _skip_renumber_nodes_and_**elements = _skip_renumber_nodes_and_**elements
> ||
> skip_renumber_nodes_and_**elements;
>
> makes the member variable true, and then
>
> if(!_skip_renumber_nodes_and_**elements)
> this->renumber_nodes_and_**elements();
>
> shouldn't call the renumbering.
>
> Assuming I'm not just missing something obvious, could you step
> through in a debugger and see which step of that is failing?
> ---
> Roy
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
