|Status:||Archived||Start date:||16 Apr 2013|
|Target version:||Sprint 20|
Should it be an application-wide registry of materials? Does it need to be Singleton?
Is its usage not too cumbersome for the user?
see also item #162
- Simplify change of properties of existing materials, including material name, refractive index (const -> to non-const ?)
to make life in MaterialBrowserView easier
- Provide UnitTests for MaterialManager
#6 Updated by pospelov about 7 years ago
- Priority changed from Normal to High
- Found out the bug in MaterialVisitor & MaterialManager behavior:
Attempt to create HomogeniousMaterial with the name of previously created HomogeneousMagneticMaterial will lead to appearance of MagneticMaterial in the sample instead of expected normal one.