Error running script: ask[list[λ[when green flag clicked]+/-][+/-]]and wait

[onu032001]

As this post is not resolved at all, I will mention the error again.

Content

If you don’t see the image, the plain-text source is here:

when green flag clicked
ask[list[λ[when green flag clicked]+/-]+/-]and wait

This produces a dialog with the following option:

Context >> a HatBlockMorph ("when $greenflag clicked...") a VariableFrame {}

This is a serious bug. Please fix this.

Footage

[mark4sisb]

You can just bump the old topic in this case. This wouldn’t be considered necroposting (I don’t think) if you explain why you think this issue is important (ie an example where you ran into it) and that you are bumping to ensure developer attention (ie because there was no developer response originally acknowledging the bug). But creating a new topic certainly isn’t the best forum etiquette.

[codingisfun2831t]

@owlsss

This is less of a bug, and more of a mis-feature. It’s spitting out the Morphic markup because you can’t have a menu with a block as an option. I believe this also used to happen with years ago

@onu032001

This is a serious bug. Please fix this.

Not serious in the slightest.. This is a “bug” that will only happen IF you ask something like that (which why would you want to do in the first place) and you get a bad result.

[codingisfun2831t]

Although:

@sathvikrias

@petermathijssen

a funny way

not really that strange, imho.

what the op is doing is intended. no problems occur using commands and reporters when asking a list.

in snap, asking a list results in a menu. If you want to have normal blocks in the menu, you can, giving the user of the program a choice as to what the sprite will do. you should be able to ask for hats in a menu, since everything is theoretically first-class. an example use case for this is asking the user what event the project should start listening for, chosen by a dialog with hats.

This would be kindof useful. Other ring types already support stuff like that, so hats should also. Now maybe using this:

should work, and it wont have the ring shape.

[bh]

@onu032001

This is a serious bug. Please fix this.

I love your enthusiasm about programming, but sometimes you have funny ideas about priorities.

Snap! 12 was a very ambitious update with a zillion new features. People have been reporting bugs about all of them, which is very helpful; I don’t at all want to discourage bug reports! Jens is on vacation right now, but he’s been working hard at responding to them.

But first class hat blocks are a pretty obscure feature to begin with. I’ve been programming in Snap! for over a decade now, and I’ve never felt the need for custom hat blocks that wasn’t solved by the generic WHEN block.

Don’t get me wrong; if we offer first class hat blocks they should work. I’m sure Jens will get around to this. But many things are more urgent than this.

Also, bumping bug reports doesn’t increase their priority; it’s just annoying. Maybe if someone else bumps a bug report by saying “I ran into this problem also” we might consider it more urgent. (But don’t take this to mean that you should ask all your friends to bump a bug report; we’d see through that, and it’d go past annoying into infuriating. A genuine bump of a bug report would explain some other context (for example by attaching a project link) in which the same bug came up.)

[owlsss]

It is literally just a lot of .toString() calls