From 8fe52aebc87daf126d66d9308af0643f700c5757 Mon Sep 17 00:00:00 2001 From: bangerth Date: Mon, 15 Nov 2010 01:25:37 +0000 Subject: [PATCH] Link to step-40. git-svn-id: https://svn.dealii.org/trunk@22734 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/include/deal.II/base/data_out_base.h | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/deal.II/include/deal.II/base/data_out_base.h b/deal.II/include/deal.II/base/data_out_base.h index bd583acba6..940c56c482 100644 --- a/deal.II/include/deal.II/base/data_out_base.h +++ b/deal.II/include/deal.II/base/data_out_base.h @@ -1708,10 +1708,13 @@ class DataOutBase * name rather than having to group several scalar fields into a * vector later on in the visualization program. * - * Some visualization programs, such as ParaView, can read several separate - * VTU files to parallelize visualization. In that case, you need a - * .pvtu file that describes which VTU files form a group. The - * DataOutInterface::write_pvtu_record() function can generate such a master record. + * Some visualization programs, such as ParaView, can read several + * separate VTU files to parallelize visualization. In that case, you + * need a .pvtu file that describes which VTU files form + * a group. The DataOutInterface::write_pvtu_record() function can + * generate such a master record. + * + * The use of this function is explained in step-40. */ template static void write_vtu (const std::vector > &patches, @@ -2275,6 +2278,9 @@ class DataOutInterface : private DataOutBase * call the current function, listing the * names of the files written by all * parallel processes. + * + * @note The use of this function is + * explained in step-40. */ void write_pvtu_record (std::ostream &out, const std::vector &piece_names) const; -- 2.39.5