m (Asqwde moved page Talk:List of Misconceptions aAout Scratch to Talk:List of Misconceptions About Scratch without leaving a redirect: oops)
m (Kenny2scratch moved page Talk:List of Misconceptions About Scratch to Talk:List of Misconceptions about Scratch without leaving a redirect: revert - capitalizing "about" puts emphasis in the wrong places)
 
(No difference)

Latest revision as of 03:48, 26 September 2018

The following sections are empty:

  • UI
  • Scratch Wiki
  • Scratch FAQ
  • Project Player

The rest need more examples of misconceptions.
3sal2 (talk | contribs) 00:13, 19 June 2013 (UTC)

How many of these are actual misconceptions?

Out of the following list, I haven't seen a single example of somebody thinking that:

  • If-then loop
  • Report only being for inappropriate material
  • Lack of a dustbin

In addition, is the Kaj section even necessary?
jvvg (talk | contribs) 16:31, 22 October 2014 (UTC)

Lightnin on the "forever if" block. One down...
Djdolphin (talk | contribs) 17:54, 22 October 2014 (UTC)
Where did you see it saying that report was only for inappropriate material?
ErnieParke (talk | contribs) 00:06, 23 October 2014 (UTC)
Scratch Website → Forums
jvvg (talk | contribs) 00:09, 23 October 2014 (UTC)
I don't see it saying that:
"The Report button is not only useful for reporting inappropriate material. It has other uses, too. For instance, moving forum topics when they are not in the right one is done by reporting."
What I read is that the report button can be useful for things other then inappropriate material.
ErnieParke (talk | contribs) 00:26, 23 October 2014 (UTC)
Now that you mention it, there aren't many real misconceptions.
derpmeup (talk | contribs) 02:13, 23 October 2014 (UTC)
I noticed people being afraid to report things. It was one of the misconceptions i tried to dispel during my period as a mod.
Scimonster (talk | contribs) 19:02, 23 October 2014 (UTC)

TheLogFather's misconception suggestions

He posted these on the forums when ErnieParke asked, but they were never edited into the wiki. I'm not really competent to understand them all, but here they are.

It is not true that:

  • loops continue to run concurrently across scripts while a non-refresh script is running
  • sensors in booleans sent as parameters into custom blocks can change the parameter's value while the custom block script is running (e.g. “key space pressed?” etc.)
  • “touching mouse-pointer” isn't sensed by a hidden sprite (maybe it's more likely that the possibility just wasn't even considered…?)
  • using non-refresh custom blocks is the same as turbo mode (kinda related to first one, I guess)
  • the use of Stage3D in the Scratch source code means Scratch will soon have built-in 3D capability
  • “when key - pressed” hat blocks are broken (because they behave so erratically compared to boolean sensor)
  • broadcasts only received by the original sprite, not clones (again, probably not even considered, until ‘hit’ by it)
  • the layer number is like a ‘depth distance’ (rather than a position in a stack), so going back by 998 layers is different to going back 999
  • Floating-Point numbers are exact (e.g. start with value 1, and subtract 0.1 ten times - help! why is answer not zero!?!? Why is cos(90) not zero? Why is tan(90) not infinity? etc.)
  • sin, cos, tan functions use radians (mostly a trap for the more experienced coder coming to Scratch!)


-unsigned comment by Noumenon72 (talk | contribs)

I did add some of the misconceptions, just not all of them because some of them seemed obscure. Thanks for posting the list here though! :)
ErnieParke (talk | contribs) 17:33, 15 December 2014 (UTC)