m
Line 18: Line 18:
 
[[Category:Community]]
 
[[Category:Community]]
 
[[Category:Scratch Wiki Bugs]]
 
[[Category:Scratch Wiki Bugs]]
 
==Boolean blocks==
 
[[Boolean Block|Boolean blocks]] are shaped like [[Reporter Block|Reporter blocks]].
 
<scratchblocks>say <mouse down?></scratchblocks>
 
:[http://github.com/blob8108/scratchblocks2/issues/17 Added #17].
 
I can do angled ''empty'' boolean slots easily enough, because they have a fixed height. [http://cl.ly/image/333H0m1u2Q3T pic] <scratchsig>Blob8108</scratchsig> 11:31, 1 September 2013 (UTC)
 
 
==Spaces==
 
Some blocks appear obsolete when there is a space between the argument and the last character.
 
<scratchblocks>set size to (100) %
 
<color [#FF0000] is touching [#FF0000] ?></scratchblocks>
 
:MediaWiki is sneakily converting those spaces into non-breaking spaces. I'll have a play with the wiki extension and see if I can stop that. <scratchsig>Blob8108</scratchsig> 13:06, 19 May 2013 (UTC)
 
:[http://github.com/blob8108/mw-ScratchBlocks2/issues/1 Added]
 
<!-- There is a link to this section from the GitHub issue -->
 
 
==Bottoms of C blocks==
 
The lengths of the bottoms of C blocks do not match the lengths of their tops and are too short.
 
<scratchblocks>when gf clicked
 
forever if <loud?>
 
turn ccw (1) degrees
 
ask [Hello, I'm Scratch Cat. What's your name?] and wait
 
if < (answer) = [XYZ] >
 
say [Wow. Wow! WOW!!!] for (2) secs
 
end</scratchblocks>
 
:I spent a good while trying to do this one, but I think it's probably a CSS limitation. I'm not sure it's worth fixing, either. <scratchsig>Blob8108</scratchsig> 08:27, 11 June 2013 (UTC)
 
:There's a trivial JS fix for this, but it causes nasty flickering when the page refreshes.  <scratchsig>Blob8108</scratchsig> 11:50, 11 June 2013 (UTC)
 
[http://github.com/blob8108/scratchblocks2/issues/8 Issue #8]
 
 
== Repeating arrows ==
 
 
C Blocks that repeat need the arrows at the bottom.
 
<scratchblocks>
 
repeat (10)
 
move (5) steps
 
end</scratchblocks>
 
<scratchsig>Mathfreak231</scratchsig> 00:54, 28 July 2013 (UTC)
 
:Added [https://github.com/blob8108/scratchblocks2/issues/23 #23].
 
 
:How boring. I really can't be bothered to do this one. :P
 
:Sci knows CSS, he can fix it! :D <scratchsig>Blob8108</scratchsig> 19:26, 31 August 2013 (UTC)
 
 
== {{b|Stop ()}} block when "other scripts in sprite" ==
 
 
The {{b|Stop ()}} block should render as a stack when set to "other scripts in sprite".
 
I'll add it on GitHub when I get the chance, probably tomorrow.
 
<scratchblocks>stop [other scripts in sprite v]</scratchblocks>
 
<scratchsig>Mathfreak231</scratchsig> 21:29, 23 September 2013 (UTC)
 
 
== Lego We-Do/SensorBoard blocks wrong color ==
 
 
They changed the color to black. The plugin should do so as well.<scratchsig>Mathfreak231</scratchsig> 00:05, 9 November 2013 (UTC)
 
:Yeah, fixed in the rewrite I'm working on. :) <scratchsig>blob8108</scratchsig> 20:36, 9 November 2013 (UTC)
 
 
== 10^ ==
 
 
On the forums <scratchblocks>([10^ v] of ())</scratchblocks> appears as a Sensing block. <scratchsig>3sal2</scratchsig> 01:36, 4 August 2014 (UTC)
 
:This is only for bugs on the Wiki <scratchsig>derpmeup</scratchsig> 22:31, 3 October 2014 (UTC)
 
:Fixed, eventually <scratchsig>blob8108</scratchsig> 19:54, 28 November 2014 (UTC)
 
 
==Boolean insert in custom-arg block==
 
The outlines of an empty boolean insert of a custom-arg block appear red as obsolete instead of actual pruple. [http://blob8108.github.io/scratchblocks2/#report%3C%3E%3A%3Acustom-arg Example]
 
<scratchsig>DevanWolf</scratchsig> 01:31, 9 October 2014 (UTC)
 
 
== Plugin Not Taking Place ==
 
 
Although my always on does not pass acid3, this is still a bug. all blocks appear just as text in code tags, for example:
 
 
<sb>when gf clicked</sb>
 
 
<code>when gf clicked</code>
 
 
I see 'em the same. <scratchsig>Krett12</scratchsig> 00:58, 8 October 2014 (UTC)
 
:You're not making sense. <scratchsig>blob8108</scratchsig> 19:55, 28 November 2014 (UTC)
 
 
==Extension Blocks==
 
No new extension blocks. Old ones work fine.
 
<scratchblocks>
 
when [slider v] [> v] (50)
 
 
when distance [< v] (20)
 
 
when tilt [= v] (1)
 
 
turn [motor v] on for (1) secs
 
 
turn [motor v] on
 
 
turn [motor v] off
 
 
set [motor v] power to (100)
 
 
set [motor v] direction [this way v]
 
 
when distance < (20)
 
 
when tilt = (1)
 
 
turn motor on for (1) secs
 
 
turn motor on
 
 
turn motor off
 
 
set motor power (100)
 
 
set motor direction [this way v]
 
</scratchblocks>
 
<scratchsig>DevanWolf</scratchsig> 15:24, 28 November 2014 (UTC)
 
 
==Scratch Wiki Extension block color==
 
In the [http://scratch.mit.edu/discuss Scratch Forums] and [http://blob8108.github.io/scratchblocks2#(%5Bslider%20v%5Dsensor%20value) blob8108's block renderer], all extension blocks, such as Lego WeDo and PicoBoard appears to be grey as normal. But in the Scratch Wiki, all extension blocks are purple instead.
 
<scratchblocks>([slider v] sensor value)</scratchblocks>
 
<scratchsig>DevanWolf</scratchsig> 15:34, 28 November 2014 (UTC)
 
:Right, so that just means the wiki's out of date. This is not a bug in the plugin. Please don't report things here that aren't a bug in the plugin (with the exception of [[#Spaces]]). <scratchsig>blob8108</scratchsig> 19:49, 28 November 2014 (UTC)
 

Revision as of 20:01, 28 November 2014

Shortcut:


Note Warning: This page is very probably out of date. Try the issue tracker on GitHub. (Although you might still like to discuss bugs here before reporting them.)

This page is a list of bugs in the new 2.0 Block Plugin by blob8108.

The wiki usually lags behind the latest version of the plugin. Before reporting a bug, please test it on the plugin test page. If the bug doesn't happen there, then all you've found is that the wiki's out of date. Go bug scmb1 to update the wiki or something.

If you have a Github account, it'd be awesome if you could add the bug directly to the issue tracker.

Otherwise, click "Add Topic" at the top to add a bug. Be descriptive and give an example. Write the example here in a <scratchblocks> tag, sign with four tildes (~~~~), and also provide a link to the test page showing the same example. Thanks!

You can comment on a bug like you can on a talk page. Just remember to indent your post(s) and sign them.

The archive can be found here. Move finished discussions there.