1.4 currently has a broadcast to run the project. (scratch-startclicked), and I propose a new broadcast:
scratch-turboon
and
scratch-turbooff
These would en/disable turbo mode. They could be useful for 3D projects, or ones with huge repetition.
What do people think.
Vote for it here
Please if you do support, but cannot spare a vote, can you leave a comment on the suggestions page.
Last edited by johnnydean1 (2011-05-01 16:43:55)
Offline
It makes sense, I guess. The only problem is that somebody new to Scratch could be really confused about it, and even, perhaps, unintentionally put the project into Turbo Mode and get highly confused about what to do next; their project wouldn't run as expected.
Offline
coolstuff wrote:
It makes sense, I guess. The only problem is that somebody new to Scratch could be really confused about it, and even, perhaps, unintentionally put the project into Turbo Mode and get highly confused about what to do next; their project wouldn't run as expected.
Well it would be like the scratch-startclicked broadcast. Many people do not know it is there. This would not push new members away as it would be a hidden feature.
Offline
I support!
Offline
Offline
Hmm, it sounds resonable... I might vote for it.
Offline
Why not... I support (even though I'm not wasting a vote on it)
Offline
Please if you do support, but cannot spare a vote, can you leave a comment on the suggestions page.
Offline
Yessss, this gives all the advantages of turbo without the hassle or forcing the user to shift click. Voted
Offline
archmage wrote:
Yessss, this gives all the advantages of turbo without the hassle or forcing the user to shift click. Voted
Exactly what I wanted.
Offline
johnnydean1 wrote:
Please if you do support, but cannot spare a vote, can you leave a comment on the suggestions page.
OK, will do!
In fact, given it 2 (!!!) votes
Offline
I don't think that shift-clicking is a hassle... but it would be nice to automatically start out in turbo mode.
Offline
Good work guys!
Offline
I would say that the broadcast scratch-startclicked and scratch-mousclickevent, were both a mistake, they were secrets that were like errors that the scratch team hoped no one would find. Anyways, making a broadcast like that would be kinda, dumb, no-offence. Why not just ask for a block? There could be a block which would have set single stepping speed to. The insert would be a special number dropdown, like the instrument one, it would have, (0) Turbo speed, (1) Normal, (30) Flash blocks fast, (200) Flash blocks slow. Then you could do numbers in-between to make it flash at different speeds.
Offline
Pecola1 wrote:
I would say that the broadcast scratch-startclicked and scratch-mousclickevent, were both a mistake, they were secrets that were like errors that the scratch team hoped no one would find. Anyways, making a broadcast like that would be kinda, dumb, no-offence. Why not just ask for a block? There could be a block which would have set single stepping speed to. The insert would be a special number dropdown, like the instrument one, it would have, (0) Turbo speed, (1) Normal, (30) Flash blocks fast, (200) Flash blocks slow. Then you could do numbers in-between to make it flash at different speeds.
Of course you would ask for a block for 1.7 (+0.3). LOL XD
Offline
Come on guys!
Offline
johnnydean1 wrote:
1.4 currently has a broadcast to run the project. (scratch-startclicked), and I propose a new broadcast:
scratch-turboon
and
scratch-turbooff
These would en/disable turbo mode. They could be useful for 3D projects, or ones with huge repetition.
What do people think.
Vote for it here
Please if you do support, but cannot spare a vote, can you leave a comment on the suggestions page.
3 Votes!
Offline
Pecola1 wrote:
I would say that the broadcast scratch-startclicked and scratch-mousclickevent, were both a mistake, they were secrets that were like errors that the scratch team hoped no one would find. Anyways, making a broadcast like that would be kinda, dumb, no-offence. Why not just ask for a block? There could be a block which would have set single stepping speed to. The insert would be a special number dropdown, like the instrument one, it would have, (0) Turbo speed, (1) Normal, (30) Flash blocks fast, (200) Flash blocks slow. Then you could do numbers in-between to make it flash at different speeds.
Exactly this. The fact that you can use Scratch-StartClicked and Scratch-MouseClickEvent in broadcast blocks is just a little unintentional quirk, and the block idea is cool.
Offline
meowmeow55 wrote:
Pecola1 wrote:
I would say that the broadcast scratch-startclicked and scratch-mousclickevent, were both a mistake, they were secrets that were like errors that the scratch team hoped no one would find. Anyways, making a broadcast like that would be kinda, dumb, no-offence. Why not just ask for a block? There could be a block which would have set single stepping speed to. The insert would be a special number dropdown, like the instrument one, it would have, (0) Turbo speed, (1) Normal, (30) Flash blocks fast, (200) Flash blocks slow. Then you could do numbers in-between to make it flash at different speeds.
Exactly this. The fact that you can use Scratch-StartClicked and Scratch-MouseClickEvent in broadcast blocks is just a little unintentional quirk, and the block idea is cool.
It probably was unintentional and only meant for easy transferring between framemorph and spritemorph, but it's still a useful feature. A completely new block would probably be rejected by the ST, and would be disturbing to new starters.
Offline
johnnydean1 wrote:
1.4 currently has a broadcast to run the project. (scratch-startclicked), and I propose a new broadcast:
scratch-turboon
and
scratch-turbooff
These would en/disable turbo mode. They could be useful for 3D projects, or ones with huge repetition.
What do people think.
Vote for it here
Please if you do support, but cannot spare a vote, can you leave a comment on the suggestions page.
please note that the "scratch-startclicked" does not work in flash
Offline
I think this is a very good idea. I have a lot of projects that don't work as well out of turbo mode, so I ask people to play them in it, but half of them don't know what it is!
Also, why is everyone saying that you have to shift-click something to get into turo mode?
EDIT: oh, also Scratch-StartClicked is there because that's the event fired by the green flag. I'm not sure about Scratch-MouseClickEvent.
Last edited by ScratchReallyROCKS (2011-05-08 09:48:18)
Offline
ScratchReallyROCKS wrote:
I think this is a very good idea. I have a lot of projects that don't work as well out of turbo mode, so I ask people to play them in it, but half of them don't know what it is!
Also, why is everyone saying that you have to shift-click something to get into turo mode?
EDIT: oh, also Scratch-StartClicked is there because that's the event fired by the green flag. I'm not sure about Scratch-MouseClickEvent.
you have to hold down the shift key and press the green flag to enter turbo mode
Offline
scimonster wrote:
Pecola1 wrote:
I would say that the broadcast scratch-startclicked and scratch-mousclickevent, were both a mistake, they were secrets that were like errors that the scratch team hoped no one would find. Anyways, making a broadcast like that would be kinda, dumb, no-offence. Why not just ask for a block? There could be a block which would have set single stepping speed to. The insert would be a special number dropdown, like the instrument one, it would have, (0) Turbo speed, (1) Normal, (30) Flash blocks fast, (200) Flash blocks slow. Then you could do numbers in-between to make it flash at different speeds.
Of course you would ask for a block for 1.7 (+0.3). LOL XD
Scratch 1.7?
Offline