I mean, you can also just go into the pen category and click the block, you don't even need to drag it out.
Sure, but I always put a reset block in the scripting area because I'm not always in the pen category, infact, the amount of time I spend in the pen category is... extremely small. I think I'm most often in the variables or control, so having to switch to pen just to find out why my project is going beserk, is annoying, so instead, I put reset in the scripting area, and when I come up with the pen equivalent, it will be too.
You do you, I guess
Basically. Yeah. No the real lesson here, is even though I understand how powerful snap is, there's always elements I just... don't use. Which is why I tend to struggle with simple stuff. Well. "simple" stuff.
I actually spend more time in custom blocks actually, thinking about it.
That's pretty much the same for me.
microworld library?
Oh they've already done that! Awesome. (Of course Jens hated the idea when I suggested it...)
I mean, I’m not entirely sure if it’s possible, but there were some things that looked similar to what you were saying there.
Yeah, it looks that way to me too. :~)
Sorry to butt in (and probably ask an idiotic question), but I'm not seeing when (position) changes::hat control anywhere in dev mode. Was it removed no longer than 11 hours ago?
It's in the Events library
Ah. Knew it was a stupid question. 
Do those exist?
Jens doesn't believe in this for some reason. That and constantly updating variable watchers
Well that's clearly for performance reasons. If you have to run a display refresh every time you change a variable, your computer won't have any time to run your actual program.
OK, I guess not, but I just sound like an idiot.
Thr thing is, I don't see why it can't refresh almost immediately. Firstly, the watcher would only need to refresh when the value changes, it doesn't need to be a constant refresh, since the set variable function can just schedule a watcher refresh the next time the screen refreshes. Plus, if the value inside is an object, like a sprite or a list, that is it's own morph, which handles it's own refreshing. For the case of lists, they can do the same thing, scheduling a refresh when the list gets modified (if the list is being shown on screen anyway).
Of course what also convinces me that this shouldn't be much of an issue, is because if you're constantly writing the value on stage in a forever loop, that updates immediately, which shows that snap should be able to handle it. Just refresh the watchers when the stage refreshes.
Oh I thought the request was for every SET invocation to cause an immediate refresh. Are watcher updates less frequent than stage refreshes? Shows how little attention I pay to watchers... :~)
Last time when I looked at this, variable watchers were updated at 2 FPS.
With the advance of events/rules, especially "when changed", some kind of notification will be created, for sure.
But why is the instant refresh so important for you guys?
As debug tools or UI elements?
There was also a cymplecy custom variable watchers, published some time ago as a part of the Mayflower project.
Both, really