PAUSE ALL inside a WARP does something I don't understand

[brianharvey]

https://snap.berkeley.edu/snap/snap.html#present:Username=bh&ProjectName=The%20Sierpi%C5%84ski%20Triangle

This is a copy of a project a user posted in the forum, into which I've inserted a PAUSE ALL block to try to help me understand the logic of the user's code. (They do the work on the way down in the recursion, by drawing the outermost triangle right side up and then recursively drawing upside down triangles. I'm accustomed to doing the work on the way up in the recursion, drawing a zillion tiny right side up triangles.)

Anyway, I put the PAUSE ALL inside a WARP that was already in the user's project. What I expected to happen was that the PAUSE would temporarily undo the WARP, show on the stage what the code has drawn so far, and then resume the WARP when I press the yellow Play button. What actually happened is that pressing PLAY repeatedly had no visible effect, but pressing the red Stop button caused the entire Sierpinski gasket to appear.

I'm not sure if it's always been like this and I never noticed, or if it's a recently-ish introduced behavior. Is this a bug or a feature? If it's a feature, please help me understand its behavior.

P.S. If I remove the WARP, then the PAUSE behaves as I expect, so it's definitely because of the WARP that it does what it does.

[Mark4SISB]

Upon some investigation, it seems that PAUSE ALL in a WARP is doing exactly what you expect except refresh the stage. If you exit/enter fullscreen, a stage refresh will be forced and you'll see your progress thus far. The reason pressing pause seems to do nothing is because of a) How quickly the program reaches the next pause, and b) Your example is recursively running PAUSE ALL, so you need to unpause a lot of times for the WARP to finish and the stage to refresh.