Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 317 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
love2d similitude?
MoKaLux
Member
how are you all doing?
I just had this question in my head
In love2d you have:
- love.load
- love.draw
- love.update
- love.keypressed
Each "functions" has its own goal.
Do you think it would be good practice to do the same in gideros?
- gideros.init
- gideros draw (n/a ?)
- gideros.ENTER_FRAME
- gideros KEY_UP, KEY_DOWN
For now what I do is set a flag to true/false when a key is pressed/released and in ENTER_FRAME I check for the key flag to do some actions.
Would it be better to do it in KEY_DOWN/KEY_UP, or does it even matter ?
Thank you
I just had this question in my head
In love2d you have:
- love.load
- love.draw
- love.update
- love.keypressed
Each "functions" has its own goal.
Do you think it would be good practice to do the same in gideros?
- gideros.init
- gideros draw (n/a ?)
- gideros.ENTER_FRAME
- gideros KEY_UP, KEY_DOWN
For now what I do is set a flag to true/false when a key is pressed/released and in ENTER_FRAME I check for the key flag to do some actions.
Would it be better to do it in KEY_DOWN/KEY_UP, or does it even matter
?Thank you
my growING GIDEROS github repositories: https://github.com/mokalux?tab=repositories
Tagged:
Comments
Gideros has an Event.KEY_UP event, what's stopping you from using it to receive a button click?
Likes: MoKaLux
Fragmenter - animated loop machine and IKONOMIKON - the memory game