Although Textures::declare manages the task of declaring and any subsequent reconfiguration, it does not update any logical textures which may have already been derived from it. Consequently defining textures should only occur once all declarations within that scheme have been made.
Unlike other texture schemes, registration order in the flats scheme is from newest to oldest and thus one must first check whether a flat is already declared before doing so.
Added by danij almost 12 years ago
Added by
Fixed: Replacement flat texture registration
Although Textures::declare manages the task of declaring and any
subsequent reconfiguration, it does not update any logical textures
which may have already been derived from it. Consequently defining
textures should only occur once all declarations within that scheme
have been made.
Unlike other texture schemes, registration order in the flats scheme
is from newest to oldest and thus one must first check whether a flat
is already declared before doing so.