Refactoring #1649

Ensure consistent use of ambientMaterial

Added by wuttke about 4 years ago. Updated 2 months ago.

Status:ResolvedStart date:19 Nov 2016
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


Is ambientMaterial==nullptr allowed?
If no, prevent it from ever occuring.
If yes, make sure we don't call *ambientMaterial without prior check.


#1 Updated by wuttke almost 4 years ago

  • Parent task changed from #1290 to #1645

#2 Updated by herck over 3 years ago

  • Status changed from New to Resolved

This issue is resolved during a refactoring: materials are no longer polymorphic and are not stored as pointers anymore

#3 Updated by wuttke 2 months ago

  • Parent task deleted (#1645)

Also available in: Atom PDF