Points
Points in a script. So, like the comment block did nothing, the point block would do nothing. It would look something like
| Point [ ] |
And in the box, you would type in any word.
Then, you would use other point scripts to use those script points. Such as returning to that point in the script.
| Return to point [ ] |
———
Regions
This would be the "true" area of a sprite. It would be good in buttons, where, although the button may be a specific shape, you want it to report being clicked, when a region is clicked.
To not confuse people, this would be like the set centre of sprite function, where it is set automatically unless changed manually.
It would also be useful for <touching [ |v]> blocks. For example, a pacman sprite often get's stuck because it's mouth area touches the wall, then it turns, and because pacman is not a complete circle but has a cut-out as a mouth.
If you have no idea what I'm talking about, tell me.
Supporters wrote:
-jji7skyline
-Death_Wish
-JJROCKER
-scimonster
Last edited by jji7skyline (2011-09-13 18:46:56)
Offline
bump
Offline
I support both
Actually, the first one would be easy with a When I receive <broacast> block, being like <broadcast[ ]and wait c> except When <broadcast> received
Offline
Death_Wish wrote:
I support both
![]()
Actually, the first one would be easy with a When I receive <broacast> block, being like <broadcast[ ]and wait c> except When <broadcast> received![]()
Yea I guess
Offline
bump
Offline
jji7skyline wrote:
bump
I don't get it. E'splain?
Offline
Trekkie210 wrote:
jji7skyline wrote:
bump
I don't get it. E'splain?
Points would allow you to go back, or to go forward to a particular point in any script.
Regions would specify how large a sprite is
Offline
I'm afraid that I strongly disagree with your "points" idea. That's effectively the same as having a "goto" command (common in simple languages such as BASIC) which is largely regarded as leading to sloppy, disorganized code. Because of this, and because there are much better ways to do this, more powerful languages almost never have this. Since Scratch is about learning to program, I think it would be counter-productive to encourage a technique that is useless later on.
As for regions, I think I saw a similar suggestion like this before. I opposed it before, (on the grounds that you could achieve the same effect with a sensor sprite) but I am beginning to see its merits. I think it could be very useful.
Offline
Harakou wrote:
I'm afraid that I strongly disagree with your "points" idea. That's effectively the same as having a "goto" command (common in simple languages such as BASIC) which is largely regarded as leading to sloppy, disorganized code. Because of this, and because there are much better ways to do this, more powerful languages almost never have this. Since Scratch is about learning to program, I think it would be counter-productive to encourage a technique that is useless later on.
As for regions, I think I saw a similar suggestion like this before. I opposed it before, (on the grounds that you could achieve the same effect with a sensor sprite) but I am beginning to see its merits. I think it could be very useful.
Oh... I didn't realise that... but I thought it would be a cool way to use recursion, which I thought was a common feature in many languages...
As for regions, it would help avoid having to make sensor sprites for every button on a OS
Offline
Harakou wrote:
I'm afraid that I strongly disagree with your "points" idea. That's effectively the same as having a "goto" command (common in simple languages such as BASIC) which is largely regarded as leading to sloppy, disorganized code. Because of this, and because there are much better ways to do this, more powerful languages almost never have this. Since Scratch is about learning to program, I think it would be counter-productive to encourage a technique that is useless later on.
As for regions, I think I saw a similar suggestion like this before. I opposed it before, (on the grounds that you could achieve the same effect with a sensor sprite) but I am beginning to see its merits. I think it could be very useful.
That would be true, if you could do OOP in Scratch. Do you know a programming language other than Scratch which doesn't have BOTH? Even C doesn't! (and you really don't want to make Scratch harder to program than C, do you?)
Offline
Support both!
Offline