A new addon for block comment alignment - #9118
Conversation
DNin01
added
type: enhancement
|
Addon details updated. |
|
While testing, I noticed that there's currently a bug that makes block comments revert to their original position after switching sprites. That makes an addon like this not very useful - maybe we should wait until it's fixed? |
How do you trigger that bug? What project(s) is it happening in? I'm not spotting any problems myself. It might have to do with the fact that the new addon's userscript overrides Edge 151 |
I thought it was a vanilla bug because I could reproduce it without your addon enabled, but disabling SA fixes it. I'll try to find the addon that is causing it. Edit: see #9151. |
Co-authored-by: Maximouse <brestl1c@outlook.com>
Remove guard, rename some variables
2 participants
Better Editor Comments addon removal
All of the addon patches in
fix-editor-commentswere fixed in the current version of Scratch (hooray! 🎉) so those settings are no longer necessary. With only the "Keep connections straight" feature left, I created a dedicated addon, "Horizontally aligned comments," to take its place.The Shift key update
I also updated how the alignment feature works. The alignment feature is nice if you like comments to be directly to the right of the block they're attached to. But what if you only want to do this for particular comments?
So, I made it require holding a key by default, and it now aligns the comment as you drag it, not just when you let go. This was inspired by snapping features in image/graphic editors.
Aligning.an.attached.comment.mp4
For users who had the "Keep connections straight" setting enabled, this addon and its "Flip controls" setting will be enabled automatically to preserve user preferences. Otherwise, both must be enabled by the user.
"New" tag behavior
This addon has both a
versionAddedandlatestUpdatein order to display an update-styled notice while still being displayed as new. Normally, this would cause a "new features" or "new settings" tag to appear next to the "new" tag, but the settings page code has been modified so that doesn't happen.I tested these changes and the setting migration works.