buttons

[sergil]

Hi!

 

I was testing buttons and I saw that for buttons I need a spritesheet. May I need creatig separate spritesheets for all the buttons or can I use a atlas texture with all the game elements and refer somewhere the normal, over and press images?

[Alvin]

Have a look at the Button constructor, when you create it, you need to specify the over,out and down frames, and the spritesheet used can be as large as you want.

[sergil]

In the buttons examples, I see that Phaser use a spritesheet and the specify the over,out and down frames, but the way I think Phaser uses the spritesheet for this examples is dividing it in 3 frames, and the the first frame is the over, the second is the out and the third is the down.

 

If I use a texture atlas with all the sprites of the game (which will be of different sizes), how can I know which frame will be the over,out and down ? Playing with shoebox, I realize that sometimes it constructs the atlas with the sprites in different order, and the normal way to call the frames will be by sprite name?

 

What do you think?

[sergil]

I haven't find the solution yet...

[haden]

When you use a texture atlas, for example with Shoebox, each frame is stored in the atlas with it's filename as an ID. In phaser you can pass that ID instead of frame number. You can find a good example in the Basic project template (look into phaser/ressources/basic), especially MainMenu.js

[sergil]

Wow!!!! I will test this!!!

 

thanks a lot!