Scratch

Thanks for all the helpful bug reports!

Player updated! If you go to a project page w/ flash player, open your console (F12 on Chrome, click "console") and reload, you should see "version 149" now. If not, clear your cache.

Changes:
- disappearing full-screen button and top-bar size issues
- can't get into edit mode (Sorry everyone. We don't want people sharing projects that you can't download and open on Scratch 1.4)
  - some of the performance issues addressed (If you reported laggyness upthread here, please test and let us know if it's fixed!)

OS: Mac OSX 10.8.1 (but the problem seem to cover all platforms)
Browser: Safari 6.0 (and Internet Exploroer 7)
Flash version: 11.4.402.265
Examples of the problem:
http://scratch.mit.edu/projects/Yllie/2580576 http://scratch.mit.edu/projects/Yllie/1976643

I found a very serious glitch in the new flash player. When running some of my games the menus in the game disappear, like in Blue Box 2 (2nd link)  the buttons first slides in from the edges and then they are supposed to stop in the middle. However, in the new flash player they slide in and then quickly slides back again.
I have not noticed this problem on any other scratchers game so far but it happens on several of my own. I noticed this problem already when when I was trying Scratch 2.0 Beta. Please take a look at it as it makes my games worthless and unable to play. 
/Yllie

The game itself is resized. It's not 480 x 360 pixels. Because of this, it's resized, making text look weird.

Kenichi10 wrote:

The game itself is resized. It's not 480 x 360 pixels. Because of this, it's resized, making text look weird.

Good analysis! I've noticed that the text in many projects doesn't look good if your browser is zoomed even slightly in or out. For those projects, you can either set your browser to "actual size" or use the "full screen" button. (My browser has an "Actual size" command in the view menu.)

BoltBait wrote:

It's getting worse, not better. 

None of the issues I pointed out on page 1 of this thread have been addressed and the player seems slower now than before.

...

BTW, how do we see the player version if it not shown on the flag bar anymore?

Your bug reports are very helpful. However, it takes time to find and fix bugs. In some cases, a bug only shows up on certain browsers or OS's, and It's difficult to fix a bug until you can reproduce it. (For example the cut-off text in variable monitors bug doesn't show up in any of my browsers. I think it's probably specific to Windows, but I haven't had a chance to verify that.)

The version number is now printed in the JavaScript console; less visual clutter.

Thanks again for the great bug reports and please be patient.

Last edited by johnadmin (2012-09-12 12:13:33)

johnadmin wrote:

Your bug reports are very helpful. However, it takes time to find and fix bugs.

Sorry, didn't mean to come off as impatient.

OK, just noticed another issue:



EDIT:  Looks like my script is missing a "Show" before the "Stamp".  That may be the problem.  Interesting that it worked before.

Last edited by BoltBait (2012-09-12 13:08:19)

Thanks for the reports everyone! Player updated to v150


- added an "oldWebsite" flag to suppress embedMode (which caused full-screen buttton to disappear) and disable "setEditMode"
- bug: performance issue with color touching
- bug: flickering full-screen button
- bug: incorrect mapping of old->new midi instruments
- bug: in old project conversion (taddl/2771043, 'the run 1.0.4'; had a SensorBoardMorph on stage)
- bug: disallow switching variable monitor modes in player mode
- bug: scissors could delete blocks from palette

Thanks.

I'm happy to see some progress on the player today. 

If that is the case, then the bug on that last one is completely mine.  I'll be sure to add the "show" before the stamp.  That was my intent.

EDIT:

And, thank you very much for posting your change log each release.  That helps us figure out which bugs we should be retesting.

Last edited by BoltBait (2012-09-12 18:17:36)

I apologize in advance for fooling around in edit mode.



as you can see, if a variable name contains %b or %n, it transforms the entire variable reporter into whatever the code refers to in the squeak thing. I assume the glitch is present for %l as well.

Hopefully you didn't know about this, as I dont want to come off as being pretentious by reporting something you already know exists that i wasn't even supposed to be seeing in the first place.

I fonnd that in my game RAZOR and RAZOR 2, there is a little line inbetween the scrolling sprites. This didn't happen in the old flash player. Is it because of the changes of screen size? Thanks for looking.

Wes64 wrote:

I apologize in advance for fooling around in edit mode.

http://i48.tinypic.com/2hzqydz.jpg

as you can see, if a variable name contains %b or %n, it transforms the entire variable reporter into whatever the code refers to in the squeak thing. I assume the glitch is present for %l as well.

Hopefully you didn't know about this, as I dont want to come off as being pretentious by reporting something you already know exists that i wasn't even supposed to be seeing in the first place.

I can confirm this bug happens with %n, %b, and %s when creating them in the alpha editor.

veggieman001 wrote:

Wes64 wrote:

I apologize in advance for fooling around in edit mode.

http://i48.tinypic.com/2hzqydz.jpg

as you can see, if a variable name contains %b or %n, it transforms the entire variable reporter into whatever the code refers to in the squeak thing. I assume the glitch is present for %l as well.

Hopefully you didn't know about this, as I dont want to come off as being pretentious by reporting something you already know exists that i wasn't even supposed to be seeing in the first place.

I can confirm this bug happens with %n, %b, and %s when creating them in the alpha editor.

As can I. To bad we can't do that in 1.4   

[edit 1] %c also works to.

[edit 2] as does %m

Last edited by zubblewu (2012-09-13 12:04:04)

Some of my games are unplayable now with this new flash player. I liked the old size, the new size screws up my characters, and again, somethings and now unplayable. For example, this. Also some of my 1s1s games, like this don't work too. The background shakes, when I am telling it to go to 0, 0. Please help!

Thanks!