The one with buttons should be a reporter, reporting which button you click!
or maybe reporting a promise that completes when you click one of the buttons
I think that's more complicated than necessary. You can just LAUNCH the code that waits for the user to click a button.
true but if they do make it synchronous i'm definitely going to use it to make an asynchronous version
(or vice versa if they make it async)
Knock yourself out, but the OP is trying to make a library for general Snap! users, who are all pretty well accustomed to LAUNCH and not so much to promises. :~)
Is that like GeoCities?
Yep, but now that Yahoo! stopped it, Neocities was born. It's pretty much the same thing, but I don't know. I don't have any experience with GeoCities.
many serif fonts don't distinguish characters, and many sans fonts distinguish them just fine.
if you want a readable font, atkinson hyperlegible is the best.
pretty much any monospace font for programming is second best.
noto sans is very readable, and most serif fonts are worse than it because I looks like l.
new fonts are much better designed than the ones that came with windows 95.
YES, I was thinking about Atkinson Hyperlegible! I even added a block that adds the stylesheet to Snap! and sets the UI font to that. So if bh ever wants it, I can just toss it out here. But something happened that prevented the font from loading. I don't know what the problem is, but I'm going to try to find it.
Edit: found the bug. I forgot to add https:// to the font, so I think it was trying to load snap.berkeley.edu/<actual link> so I'm glad I found that out. I couldn't tell at first because this managed Chromebook disallowed the Inspect tool. 
The extension has MIGRATED into an extension file!
The blocks are now migrated into a new extension file. Hosted on none other than... Neocities. I did say
//I don't know where to host them, but don't be surprised if they end up on Neocities! ;)
in my original project, so... yeah. But what matters is that the project doesn't use code snippets, which one of us here really hates. Without further ado, here's the project:
and here's the extension file if you want to further tamper with it:
Yes, I guess I'd expect a font with "hyperlegible" in its name to try to make those characters distinguishable.
I point out that the technical term for those short horizontal lines at the top and bottom of its capital I (eye), the ones that make it not look like a vertical bar, is "serifs." And indeed all your serif font examples have the same capital I shape!
The little backwards-J hook at the bottom of the lower case l (ell) is indeed a relatively new piece of font design. It's fine, but the traditional serifs on lower case l also work fine.
The slanty top serif on the digit 1 distinguishes it well from those two letters (and is used in serif fonts also), but without the bottom serif it isn't super well distinguished from the digit 7.
As for slashing or dotting zeros, I agree that that makes them clearly distinguished from the letter O (although in fact I was working at IBM the day the memo came down about "henceforth we slash zeros instead of slashing letter Os," which was a real flag day because computing at IBM was mostly done with punched cards back then, and the programmers wrote their code on forms that they sent down to what in those unenlightened days we called the "keypunch girls," and we had to slash the letter (before the memo) or the digit (after), leading to different characters being punched into the card deck), but at the cost of serious ugliness, so I'm willing to compromise on truly circular letter O vs. severely cigar-shaped digit 0.
You have a Neocities too??!?!?!??!
even if it is technically a serif (i can't find anything that says definitively one way or the other) it does not make them serif fonts, and it really doesn't seem to be treated as a serif in any context i can find. the "sans" in comic sans specifically means it's not a serif font, it's the least serif looking font imaginable, and it has those strokes on the I. in many fonts it's nearly the same size as the top of a T. serifs definitely don't get taught in stroke order diagrams.
the way i see it I with the top and bottom lines and 1 with an underline are full variations like a strikethrough 7, open 4, crossed 0, and single/double story a and g
the serifs on the lowercase l is exactly what makes them harder to read! it looks the same as a capital i again, and looks even closer to a 1 than any sans font.
Yes, but it's highly unfinished.
That's on November 1, not October 31. It's also a totally different holiday.
Halloween did come from the Gaylics (jk i meant gaelics)
It's kinda cool tho! Keep up the work. Mine's at gradientman. I'm planning smth new with my two Neocitieses
Well put.
I'm definitely going to try and restyle my webpage.
Okay, I can see your argument there. Maybe you're right.
ikrrrrrrr no cap