It is not a problem of brick, it is a problem of Traits in pharo.

In brick we have a few traits that use��GLMBrickExtensionTrait, for example:

Trait named: #GLMBrickLayoutTrait
�� uses: GLMBrickExtensionTrait
�� category: 'Glamour-Morphic-Brick-Traits'

self traitComposition allTraits returns collection of 7 traits including��GLMBrickExtensionTrait. But implementation of��transformationOfTrait: refers to��transformations which is an array of 4 traits directly used by GLMBrick, so obviously��GLMBrickExtensionTrait is not found -> nil.

So��flattenDownAllTraits is broken and does not take care about "subclassing" of bricks.

Cheers,
Alex

On Sun, Feb 28, 2016 at 4:35 PM, Stephan Eggermont <stephan@stack.nl> wrote:
GLMBrickExtensionTrait & GLMBrickPropertiesTrait have a lot of duplication. They make GLMBrick flattenDownAllTraits do a MNU
as (self traitComposition transformationOfTrait: aTrait) = nil

Stephan