This is a read-only archive of the old Scratch 1.x Forums.
Try searching the current Scratch discussion forums.

#1 2008-11-30 17:00:39

deerelResearch
Scratcher
Registered: 2008-11-30
Posts: 2

Color effect - bug (or is it feature?)

Code shows more than 1000 words (it is shown directly on the background):
http://scratch.mit.edu/projects/deerelResearch/337495

Offline

 

#2 2008-11-30 17:08:51

Ricardo-san
Scratcher
Registered: 2008-11-20
Posts: 27

Re: Color effect - bug (or is it feature?)

I'll bet the player was updated for Scratch 1.3
You should upgrade.  wink

Offline

 

#3 2008-11-30 17:26:27

deerelResearch
Scratcher
Registered: 2008-11-30
Posts: 2

Re: Color effect - bug (or is it feature?)

That's why I ask and want to hear from the Scratch team, personally. I'd welcome 360, it's much better value than 200 (for me, the question is, if it is better for beginners). But what I would welcome primarily, is clearer definition of semantics (of more things, not just color effect, see other project where I'm showcasing bugs, another ones to come) and sticking to it in the future.

Offline

 

#4 2008-11-30 18:43:10

Paddle2See
Scratch Team
Registered: 2007-10-27
Posts: 1000+

Re: Color effect - bug (or is it feature?)

deerelResearch wrote:

That's why I ask and want to hear from the Scratch team, personally. I'd welcome 360, it's much better value than 200 (for me, the question is, if it is better for beginners). But what I would welcome primarily, is clearer definition of semantics (of more things, not just color effect, see other project where I'm showcasing bugs, another ones to come) and sticking to it in the future.

I took a look at the bug list that the development team is working from...there are two tickets that talk about differences between Scratch and the Java player with respect to the Change Color effect.  So I believe this issue is known to the development team.  Which behavior is "correct" I do not know.  But usually it is the Scratch behavior that is taken as the standard and the Java player is made to match it.  I (and others) have many projects built that assume the 200 model is correct.


http://i39.tinypic.com/2nav6o7.gif

Offline

 

#5 2008-11-30 19:30:34

TimeFreeze
Scratcher
Registered: 2008-08-11
Posts: 500+

Re: Color effect - bug (or is it feature?)

Someone figured out that the color online is a scale of 0-300 but offline it is 0-200.


There are 10 types of people in this world: Those who understand binary, and those who don't. --[insert unrelated transition]-- GRANDILOQUENCE FTW!

Offline

 

#6 2008-12-01 07:45:40

deerel
Scratcher
Registered: 2008-08-23
Posts: 89

Re: Color effect - bug (or is it feature?)

TimeFreeze wrote:

Someone figured out that the color online is a scale of 0-300 but offline it is 0-200.

0-360 in fact, at least in v31...

Offline

 

#7 2008-12-01 08:13:19

deerel
Scratcher
Registered: 2008-08-23
Posts: 89

Re: Color effect - bug (or is it feature?)

Paddle2See wrote:

deerelResearch wrote:

That's why I ask and want to hear from the Scratch team, personally. I'd welcome 360, it's much better value than 200 (for me, the question is, if it is better for beginners). But what I would welcome primarily, is clearer definition of semantics (of more things, not just color effect, see other project where I'm showcasing bugs, another ones to come) and sticking to it in the future.

I took a look at the bug list that the development team is working from...there are two tickets that talk about differences between Scratch and the Java player with respect to the Change Color effect.  So I believe this issue is known to the development team.  Which behavior is "correct" I do not know.  But usually it is the Scratch behavior that is taken as the standard and the Java player is made to match it.  I (and others) have many projects built that assume the 200 model is correct.

Well, what personally creates uncomfortable feelings of being just an important hassle (I'd better say "what p... me off", but language filter would probably cry and stop the message), are the reactions on the troubleshooting forum, or, more precisely, their lack. When I find a bug, I'd like to hear at least "we know of this issue, we're working on it, we'll release in about (eta)". But apart from your reactions (now, and some time before when you weren't officially "Scratch team") I heard nothing at all, even when I bumped my postings. Now, it is natural to come to the conclusion that, in fact, they don't want to hear about bugs at all and I should be glad they gave Scratch for free. Yes, it is true that I ranted about methodology they use, and I still hold this position firmly, I believe they hit the ground with their carefree position about code quality and their chasing features instead, but this should be another thread of communication. When they invite me to report the bug, and after I do, there comes no reaction, I feel betrayed.
Why not to release bug list read-only to public and react at lease with "yes, we know of it, #bugno" or "it is probably this thing: #bugno". What kind of "community" is this, when there are barriers to open communication?

Well, that's from me for the moment, deerel ;-(

Offline

 

#8 2008-12-01 08:24:28

deerel
Scratcher
Registered: 2008-08-23
Posts: 89

Re: Color effect - bug (or is it feature?)

deerel wrote:

...I believe they hit the ground with their carefree position about code quality and their chasing features instead...

And I would even be able and open to help. I think the transition from "wild now (which was great fun, but now it backfires)" to "working future (which can be great fun as well, if initial fears are overcome)" is needed and I'd be willing to lead or co-lead it. Though, I fear, there is little demand for this type of service...

And i said it's all of me... I am unable to shut up when under strong emotions ;-(

Last edited by deerel (2008-12-01 08:25:29)

Offline

 

Board footer