<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Georgia">That's a combination of odd factors.</font></p>
<p><font face="Georgia">- MenuMorph implements #morphicLayerNumber</font></p>
<p><font face="Georgia">- MenuMorph is generally added to the world
with something like "aWorld addMorphFront: self."</font></p>
<p><font face="Georgia">- PasteUpMorph>></font><font
face="Georgia">addMorphFront: ignores the method
#morphicLayerNumber, but does check the property by the same
name (and if missing assumes 100)</font></p>
<p><font face="Georgia">- so the menu ends up behind the progress
morph which does have a layer of 12<br>
</font></p>
<p><font face="Georgia">This could be fixed by either</font></p>
<p><font face="Georgia"> self setProperty: #morphicLayerNumber
toValue: self morphicLayerNumber.<br>
aWorld addMorphFront: self; startSteppingSubmorphsOf: self.<br>
</font></p>
<p><font face="Georgia">or</font></p>
<p><font face="Georgia"> aWorld addMorphInLayer: self;
startSteppingSubmorphsOf: self.<br>
</font></p>
<p><font face="Georgia">in the MenuMorph pop up method(s)<br>
</font></p>
<br>
<div class="moz-cite-prefix">On 4/30/18 5:14 PM, Chris Cunningham
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPp9i4=FkdPidwbCOX+P6gOh7ZehsrY7cRq6M1+pEct59NU05w@mail.gmail.com">
<div>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.</div>
<div><br>
</div>
</blockquote>
<br>
</body>
</html>