7 months ago

Unsandboxed jank that I could fix anytime but I can't be arsed #1: This block is broken*


*technically.

This block works entirely fine and as intended both compiled and interpreted; that is, provided if you swap the "in" and the "with" in the way the block reads.

Due to a shitty oversight I made when adding the block alongside all of the other string blocks and the multitude of headaches that came with, I swapped those 2 words around.

The problem is, the repository this mistake is in is the Blockly repository, which notoriously is a pain to make edits on, especially minor ones. It requires re-compiling which takes just long enough to be a bit annoying, but short enough to be pathetic as an excuse to not want to fix it (5 minutes).

The obvious solution would be to bundle a fix with other bug fixes or other features being added, right? Well I did! Twice!! (It might be 3 times but I only remember firmly that there were 2).

I was confident that I was going to finish something in my back catalogue of features for Unsandboxed that I bundled the tiny language fix in to updates twice. They never got pushed because I never finished them, and don't think I'll be able to any time soon.

This block is literally doomed to always read wrong. This is the kind of petty bug I hoped would never happen in this entire project, but once you see it, you can't unsee it.



0 comments

Loading...

Next up

freaky blocks 👁️🫦👁️

Honestly I'm so proud of how far I've come because a couple years ago I would've (and did) literally walked up and down the stack and it'd have been a huge mess of code.

The code I used this time is 15 lines long.

Btw if the next time we update Unsandboxed you see this weird formatting error on the procedures screen, that's intentional.

Well, not intentional, but we know about it and we know why it's there and how to fix it, it's just not in our interests to atm.

An update has been released for Unsandboxed.

Changelog is in the article.

So I can say for certain that Scratch 4.0 will depend on modern Blockly, which for now is being held together by the old GUI code from 3.0

An experiment has been released for global custom blocks.

This is what we've been working towards and it's a very scary and delicate feature that NEEDS testing.

https://experiments.unsandboxed.org/globproc/editor.html

Credit: Literature written by griffpatch.

Global custom blocks have been released for Unsandboxed.

Full changelog in the article.

Some changes have been made to the colour options for custom blocks:

- Category colours now work with high-contrast and dark mode

- You can now use a colour picker to select any colour you want

Thoughts on this shape for inline blocks?