From 42b10e775bc7bacf0437c56c7b154ff62187378d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vladim=C3=ADr=20Vondru=C5=A1?= Date: Thu, 23 Feb 2012 14:10:06 +0100 Subject: [PATCH] Removed old untrue documentation from Trade::AbstractImporter. --- src/Trade/AbstractImporter.h | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/src/Trade/AbstractImporter.h b/src/Trade/AbstractImporter.h index 8c084fa09..6ce1c1786 100644 --- a/src/Trade/AbstractImporter.h +++ b/src/Trade/AbstractImporter.h @@ -51,10 +51,9 @@ textures etc. function close() and one or more pairs of data access functions, based on which features are supported in given format.

For multi-data formats file opening shouldn't take long, all parsing should -be done in data parsing functions or even in envelope classes such as Mesh, -because the user might want to import only some data. This is obviously not -the case for single-data formats like images, as the file contains all data -user wants to import.

+be done in data parsing functions, because the user might want to import only +some data. This is obviously not the case for single-data formats like images, +as the file contains all data user wants to import.

*/ class MAGNUM_EXPORT AbstractImporter: public Corrade::PluginManager::Plugin { PLUGIN_INTERFACE("cz.mosra.magnum.Trade.AbstractImporter/0.1") @@ -100,11 +99,7 @@ class MAGNUM_EXPORT AbstractImporter: public Corrade::PluginManager::Plugin { virtual void close() = 0; /** @{ @name Data accessors - * Each function pair provides access to the data. The data are usually - * hierarchic, so in most cases scene will contain all objects, every - * object will have one of the materials, every material will have - * some shader for rendering and possibly even some textures, which are - * finally composed from images. + * Each function pair provides access to the data. */ /** @brief Scene count */