sntx

Members
  • Content Count

    2
  • Joined

  • Last visited

  1. Hi Ivan, Thanks for your quick response! I knew about clearing and filling graphics, have been reading about that already. Can I read more about this subject somewhere? I know that some properties are fast (like setting tint, for example) and others aren't. Is there some sort of reference on this? Which properties are fast to set and modify and which ones are slow? Thanks again!
  2. Dear community, Does Pixi ignore calls to set properties if the values are not changed? For example, let's say I have the following animation step function: step() { mySprite.x = someXVal mySprite.y = someYVal mySprite.angle = someAngleVal // etc... } Should I check if values have changed before setting them again? step() { if (mySprite.x !== someXVal) mySprite.x = someXVal if (mySprite.y !== someYVal) mySprite.y = someYVal if (mySprite.angle !== someAngleVal) mySprite.angle = someAngleVal // etc... } Obviously this example is simplified, it's purpose is just to illustrate my question. I'm thinking of the architecture of my application here and deciding what patterns to use. Another approach would be a dirty flag: step() { if (isDirty) { mySprite.x = someXVal mySprite.y = someYVal mySprite.angle = someAngleVal // etc... } isDirty = false } Re-stating my question: Do I need to implement a system for checking and setting only updated properties for PIXI objects or does PIXI already do this internally? As my application grows bigger, this would be an important decision, specially in terms of architecture and performance. Thanks! Santiago