Cocos2d-x built-in Particle System

From the class diagram, we can see that the Cocos2d-x has built-in 11 particles, the attributes of these particles are pre-defined, we can also modify some attributes in the program code, these attributes have been set in the instance in the previous section. Built-in Particle System

The built-in 11 particle system is described as follows:

You can call this operation to create a project. The particle blast effect belongs to the radius mode.

You can call this operation to create a project. Flame particle effect, which belongs to the gravity path mode.

You can call this operation to create a project. Fireworks particle effect, which belongs to the gravity mode.

. The particle effect is a gravity mode.

The sample code is as follows. Galaxy particle effect, which belongs to the radius mode.

You can call this operation to perform the following operations. Meteor particle effect, which belongs to the gravity mode.

You can call this operation to create a project. Vortex particle effect, which belongs to the radius mode.

The name of the object. The snow particle effect belongs to the gravity mode.

. Smoke particle effect, which belongs to the gravity mode.

. The effect of the Sun particles belongs to the gravity mode.

You can call this operation to perform operations on the object. Rain particle effect, which belongs to the gravity mode.

Each of these 11 particle systems has the following two create functions, which allow you to create particle objects.

Static participant explosion * Create ()

Static maid (INT numberofparticipant)

The numberofparticipant in the createwithtotalparticipant function is the number of particles initialized.

The attributes of these 11 kinds of particles vary depending on their emission modes.

 

 

Example: built-in Particle System

The following example shows the 11 built-in particle systems. In this example, the left figure shows an operation menu scenario. You can select the menu to go to the action scenario. In the action scenario, the effect of the selected particle system is displayed. Click the return button in the lower right corner to return to the menu scenario.

 

Next let's take a look at the specific program code. First, let's take a look at the helloworldscene. h file. Its code is as follows:

 

[HTML]View plaincopy

1. # Ifndef _ helloworld_scene_h __
2. # DEFINE _ helloworld_scene_h __
4. # Include "cocos2d. H"
5. # Include "myactionscene. H"
7. Typedef Enum ①
8. {
9. Kexplosion = 1
10. , Kfire
11. , Kfireworks
12. , Kflower
13. , Kgalaxy
14. , Kmeteor
15. , Krain
16. , Ksmoke
17. , Ksnow
18. , Kspiral
19. , Ksun
20. } Actiontypes; ②
23. Class helloworld: Public cocos2d: Layer
24. {
25. Public:
26. Static cocos2d: Scene * createscene ();
27. Virtual bool Init ();
28. Void onclickmenu (cocos2d: ref * psender );
30. Create_func (helloworld );
31. };
33. # Endif/_ helloworld_scene_h __

 

 

Code ① ~ ② Define an enumeration type actiontypes. 11 constants are defined in the enumeration type actiontypes. These 11 constants correspond to 11 menu items.

Next let's take a look at the next scenario myactionscene. Its myactionscene. H code is as follows:

 

[HTML]View plaincopy

1. # Ifndef _ myaction_scene_h __
2. # DEFINE _ myaction_scene_h __
4. # Include "cocos2d. H"
5. # Include "helloworldscene. H"
7. Class myaction: Public cocos2d: Layer
8. {
9. Cocos2d: labelbmfont * plabel; ①
11. Public:
12. Static cocos2d: Scene * createscene ();
13. Virtual bool Init ();
14. Virtual void onentertransitiondidfinish (); ②
16. Create_func (myaction );
17. Void backmenu (cocos2d: ref * psender); ③
18. };
20. # Endif/_ myaction_scene_h __

 

 

In the header file, line ① defines the labelbmfont member variable, which is used to display the name of the Particle System in the scene. The Code in line ② declares the onentertransitiondidfinish callback function, which overwrites the parent class function and will return it after the scenario appears. The Code in line ③ declares a callback function for the return menu.

The implementation code of myactionscene: myactionscene. CCP file. Its main code is as follows:

 

[HTML]View plaincopy

1. Bool myaction: Init ()
2. {
3. If (! Layer: Init ())
4. {
5. Return false;
6. }
8. Size visiblesize = Director: getinstance ()-> getvisiblesize ();
10. Auto pitmlabel = label: createwithbmfont ("fonts/fnt8.fnt", "<back ");
11. Auto backmenuitem = menuitemlabel: Create (pitmlabel,
12. Cc_callback_1 (myaction: backmenu, this ));
13. Backmenuitem-> setposition (point (visiblesize. Width-100,100 ));
15. Menu * Mn = menu: Create (backmenuitem, null );
16. Mn-> setposition (point: zero );
17. This-> addchild (Mn );
19. Plabel = label: createwithbmfont ("fonts/fnt8.fnt ","");
20. Plabel-> setposition (point (visiblesize. width/2, visiblesize. Height-50 ));
21. This-> addchild (plabel, 3 );
23. Return true;
24. }
26. Void myaction: onentertransitiondidfinish ()
27. {
28. Layer: onentertransitiondidfinish ();
30. Particle System * system;
32. Switch (this-> gettag () {①
33. Case kexplosion:
34. System = participant explosion: Create ();
35. Plabel-> setstring ("explosion ");
36. Break;
37. Case kfire:
38. System = participant fire: Create ();
39. Plabel-> setstring ("fire ");
40. Break;
41. Case kfireworks:
42. System = MAID: Create ();
43. Plabel-> setstring ("Fireworks ");
44. Break;
45. Case kflower:
46. System = MAID: Create ();
47. Plabel-> setstring ("Flower ");
48. Break;
49. Case kgalaxy:
50. System = participant galaxy: Create ();
51. Plabel-> setstring ("Galaxy ");
52. Break;
53. Case kmeteor:
54. System = MAID: Create ();
55. Plabel-> setstring ("Meteor ");
56. Break;
57. Case Krain:
58. System = MAID: Create ();
59. Plabel-> setstring ("Rain ");
60. Break;
61. Case ksmoke:
62. System = MAID: Create ();
63. Plabel-> setstring ("smoke ");
64. Break;
65. Case ksnow:
66. System = MAID: Create ();
67. Plabel-> setstring ("snow ");
68. Break;
69. Case kspiral:
70. System = MAID: Create ();
71. Plabel-> setstring ("Spiral ");
72. Break;
73. Case ksun:
74. System = participant Sun: Create (); ②
75. Plabel-> setstring ("sun ");
76. Break;
77. }
79. Size visiblesize = Director: getinstance ()-> getvisiblesize ();
80. System-> setposition (point (visiblesize. width/2, visiblesize. Height/2 ));
82. This-> addchild (system );
83. }

 

 

In the initialization scenario of the myaction: Init () function, create a particle system object in the myaction: onentertransitiondidfinish () function, instead of creating a particle system object in the myaction: onenter () function, this is because the scenario is not displayed when the myaction: onenter () function is called. If an explosion is created in the function, the particle system is displayed once. When the scenario is displayed, the explosion is over, and we will not see the effect.

Code ① ~ Line 2 creates 11 particle systems. Here, their default attribute values are used when creating particle systems. The plabel-> setstring ("XXX") function is used to set the content of the tag in the scenario, so that the name of the particle system is displayed after entering the scenario.

 

 

 

For more information, please refer to the first domestic swift book "swift development guide" for discussion. Website: http://www.51work6.com/swift.phpwelcome to the swifttechnology discussion group: 362298.pdf

 

 

 

 

 

Welcome to Zhijie IOS public classroom Platform

Cocos2d-x built-in Particle System