Patarakin в 08:12, 29 августа 2022

2022-08-29T08:12:19Z

← Предыдущая версия		Версия от 11:12, 29 августа 2022
Строка 1:		Строка 1:
	~~[[File:Clones.png\|thumb\|224px\|The hierarchy of a sprite and its clones.]]~~
	With the introduction of [[cloning]] in [[Scratch 2.0]], [[project]]s have many efficient capabilities to perform tasks without creating an extensive number of [[sprite]]s. Clones are instances of sprites, meaning they inherit the properties of the sprite but are separate objects. Clones commonly may have a slightly different task to perform than the parent sprite, but one barrier is that both clones and sprites respond to almost all of the [[Event Blocks\|event blocks]] (triggers). Therefore, a trigger specifically designed for a sprite will also be run by a clone when signaled.		With the introduction of [[cloning]] in [[Scratch 2.0]], [[project]]s have many efficient capabilities to perform tasks without creating an extensive number of [[sprite]]s. Clones are instances of sprites, meaning they inherit the properties of the sprite but are separate objects. Clones commonly may have a slightly different task to perform than the parent sprite, but one barrier is that both clones and sprites respond to almost all of the [[Event Blocks\|event blocks]] (triggers). Therefore, a trigger specifically designed for a sprite will also be run by a clone when signaled.

Строка 65:		Строка 64:

	[[Category:Scripting Tutorials]]		[[Category:Scripting Tutorials]]
	~~[[Category:Cloning]]~~
	~~[[ja:クローンとトリガースプライトを分離する]]~~

Patarakin: 1 версия импортирована

2022-07-21T08:33:14Z

1 версия импортирована

← Предыдущая версия	Версия от 11:33, 21 июля 2022
(нет различий)

scratch>SonicFanX123 321 в 11:39, 2 августа 2021

2021-08-02T11:39:32Z

Новая страница

[[File:Clones.png|thumb|224px|The hierarchy of a sprite and its clones.]]
With the introduction of [[cloning]] in [[Scratch 2.0]], [[project]]s have many efficient capabilities to perform tasks without creating an extensive number of [[sprite]]s. Clones are instances of sprites, meaning they inherit the properties of the sprite but are separate objects. Clones commonly may have a slightly different task to perform than the parent sprite, but one barrier is that both clones and sprites respond to almost all of the [[Event Blocks|event blocks]] (triggers). Therefore, a trigger specifically designed for a sprite will also be run by a clone when signaled.

== Concept ==
One way to understand the concept is with the following simple [[script]]:
<scratchblocks>
when this sprite clicked
go to x:(0) y:(pick random (-100) to (100))
repeat (10)
change x by (3)
</scratchblocks>
Contrary to its name, if a clone of the sprite containing the above script was to be clicked, the clone itself would perform the script. If only the sprite and ''not'' its clones should respond to the script, customize which triggers are run by what class (i.e. parent sprite or child clone) through the use of a [[Variable#Local Variables|local variable]]. If a local variable is not used, all clones will share the same variable.
[[File:Private var creation.png|thumb|250px|Creating a local variable.]]
Local [[variable]]s store values for individual sprites and clones, although they have the same name. For example, three clones can have a variable named "x velocity", but each clone can have its own individual value of its variable. In a similar way, a sprite can have a variable set to a particular [[string]] while every clone has it set to a different value. This concept of different variable values between classes allows one to choose which scripts are run by the parent sprite or child clones.

== Programming ==
When the [[Green Flag|green flag]] is clicked, all clones are immediately deleted but the parent sprite still exists. This is the correct time to set the sprite's variable to an indication of its class (position on the hierarchy).

=== Making clones behave differently to the parent sprite ===
<scratchblocks>
when gf clicked
set [instance v] to [sprite] //"instance" must be a private variable
</scratchblocks>
This small bit of data saved in the variable "instance" simply shows that the sprite is a sprite. "Instance" must be a [[private variable|Private Variable]] or else it will not work. Next, a script must be designated for assigning all clones a variable value that shows they are clones. The following script can accomplish this:
<scratchblocks>
when I start as a clone //a sprite cannot run this script, only clones
set [instance v] to [clone]
</scratchblocks>
The above script will ''not'' change the sprite's variable. Instead, each individual clone will have its own variable. Once this is done, the variable in conjunction with an [[If () Then (block)|if statement]] can properly designate triggers to only run for the sprite or its clones.
<scratchblocks>
when I receive [fadeAway v] //This script only works for clones
if <(instance) = [clone]> then
repeat (10)
change [ghost v] effect by (10)
end
</scratchblocks>
The above script will only work for the clones, because the sprite's variable is ''not'' set to "clone", and the sprite will not execute the blocks inside the statement. This variable method is an efficient way for debugging projects in which clones are causing trouble.

=== Making clones behave differently from each other ===
The following example shows how multiple clone types can be managed in a single sprite's scripts. Note that a value is assigned to the private variable "type" ''before'' each clone (or set of similar clones) is generated. If the parent sprite is to ignore a broadcast, its own unique value of "type" should be set ''after'' the clones have been generated but ''before'' the broadcast is expected.
<scratchblocks>
when green flag clicked
set [type v] to [ghost] //"type" must be a private variable.
create clone of (myself v)
set [type v] to [egon]
create clone of (myself v)
set [type v] to [parent]
</scratchblocks>

<scratchblocks>
when I receive [send in the ghosts v] //This script only works for clones...
if <(type) = [ghost]> then //...but can differentiate between them.
start sound (spooky moan v)
else
if <(type) = [egon]> then
say [Don't cross the streams!]
</scratchblocks>
The value of the private variable "type" is inherited by each clone from the parent sprite, which ignores the broadcast because its own value of "type" is different. This technique allows many different clone types to behave in unique ways.

== See Also ==
* [[Cloning]]
* [[Private Variables]]
* [[Sprite]]
* [[Variable]]s

[[Category:Scripting Tutorials]]
[[Category:Cloning]]
[[ja:クローンとトリガースプライトを分離する]]

Separating Clone and Sprite Triggers - История изменений

Patarakin в 08:12, 29 августа 2022

Patarakin: 1 версия импортирована

scratch>SonicFanX123 321 в 11:39, 2 августа 2021