Lightnin wrote:
I think RHY mentioned that they actually code things in two scripts, and then stick them together just at the end. So you could try that technique. Hope that helps
Good ol' RHY
Offline
Lightnin wrote:
Yes - this is a bit of a glitch.
Scratch sets aside a certain size memory buffer in which to store the image for each Script. When we designed it, we never imagined that 1S1S would become a trend, so we just set it to a size which, for most projects that use multiple scripts, is way more than you'd ever need. But with large 1S1S projects, that limit is sometimes crossed. So the picture of the script just ends. oops!
I think RHY mentioned that they actually code things in two scripts, and then stick them together just at the end. So you could try that technique. Hope that helps
Thank you for the idea! It will probably be more like 4 parts, but it's still the best way anyone has mentioned to deal with it.
Offline
Strange. I have the same problem, I'm making a 1S1S1C project, but the script disappears. Even worse is that the code that isn't showing up isn't even running, so half of my game is missing...
Offline
Well, I'm no help. And w00t! 1s1s Tetris!
Offline
nXIII wrote:
Lightnin wrote:
Yes - this is a bit of a glitch.
Scratch sets aside a certain size memory buffer in which to store the image for each Script. When we designed it, we never imagined that 1S1S would become a trend, so we just set it to a size which, for most projects that use multiple scripts, is way more than you'd ever need. But with large 1S1S projects, that limit is sometimes crossed. So the picture of the script just ends. oops!
I think RHY mentioned that they actually code things in two scripts, and then stick them together just at the end. So you could try that technique. Hope that helpsThank you for the idea! It will probably be more like 4 parts, but it's still the best way anyone has mentioned to deal with it.
Seems like it should... is it doesn't i'll try to help out.
Offline
Chrischb wrote:
nXIII wrote:
The-Whiz wrote:
I just can't figure out how to make the blocks actually work... i know how to make them, though.OK, now that I have BBCode and no 500-character limit:
1. Turn fill screen off (by shift-clicking on the R in the Scratch logo...Wow... thanks!
Man... How do you understand this stuff? I dont know how to program Squeak!
Offline
nXIII wrote:
ThePCKid...
XP is one of the slim-est OS's. It's better to use XP than Vista or 7.
Unless you have 64 bit. (ME!)
Offline
shadow_7283 wrote:
nXIII wrote:
ThePCKid...
XP is one of the slim-est OS's. It's better to use XP than Vista or 7.Unless you have 64 bit. (ME!)
I have 64-bit W7!
But I also have 32-bit WinVista *sigh*
Offline
Lightnin wrote:
Yes - this is a bit of a glitch.
Scratch sets aside a certain size memory buffer in which to store the image for each Script. When we designed it, we never imagined that 1S1S would become a trend, so we just set it to a size which, for most projects that use multiple scripts, is way more than you'd ever need. But with large 1S1S projects, that limit is sometimes crossed. So the picture of the script just ends. oops!
I think RHY mentioned that they actually code things in two scripts, and then stick them together just at the end. So you could try that technique. Hope that helps
That is a problem. This could be fixed in Scratch 2.0.
Offline
mathematics wrote:
Off-topic: What are those blocks at the blocks palette?
their operator blocks
(the only green one
Offline
what you could do is at the bit where it stops going
you could do a
broadcast [NEXTSCRIPT v]and at the top start a new script that carries on what you are doing
when I recive [NEXTSCRIPT v] what ever you are doing
Offline
kieran1000 wrote:
what you could do is at the bit where it stops going
you could do abroadcast [NEXTSCRIPT v]and at the top start a new script that carries on what you are doingwhen I recive [NEXTSCRIPT v] what ever you are doing
That's not 1s1s though.
Offline