That's a combination of odd factors.

- MenuMorph implements #morphicLayerNumber

- MenuMorph is generally added to the world with something like "aWorld 
addMorphFront: self."

- PasteUpMorph>>addMorphFront: ignores the method #morphicLayerNumber, 
but does check the property by the same name (and if missing assumes 100)

- so the menu ends up behind the progress morph which does have a layer 
of 12

This could be fixed by either

     self setProperty: #morphicLayerNumber toValue: self morphicLayerNumber.
     aWorld addMorphFront: self; startSteppingSubmorphsOf: self.

or

     aWorld addMorphInLayer: self; startSteppingSubmorphsOf: self.

in the MenuMorph pop up method(s)


On 4/30/18 5:14 PM, Chris Cunningham wrote:
> While doing this, bringing up the debug menu brought the menu up UNDER 
> the progress morph (visually), but the debug morph was still active 
> even though it is under the progress morph.  Very weird.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180430/517dd1cc/attachment.html>