Is there any docs for display.setDrawMode()? Other than “forceUpdate” as a parameter, what other options are there?
Thanks,
Dave
The docs still need updating.
If you use a filter that’s time-based (e.g. “filter.wobble”), there’s technically no invalidation of any display object, so Corona doesn’t know it needs to render the scene to let the filter vary over time. “forceUpdate” is a very heavy hammer for the following situation. Eventually, we’d like to make it smarter so that if there is a filter that’s time based, Corona knows to update, but for now, we’re pushing the responsibility to you all 
The other mode that’s interesting is “wireframe”. It’s very similar to the physics debug draw modes, which we’re also considering adding as parameters, but we haven’t decided if they are orthogonal to these draw modes yet.
Does it matter where this is used (e.g. as the app starts, in enterframe…etc.)? And is it a one-time setting?
Thanks,
Dave
No, it’s a dynamic setting
The docs still need updating.
If you use a filter that’s time-based (e.g. “filter.wobble”), there’s technically no invalidation of any display object, so Corona doesn’t know it needs to render the scene to let the filter vary over time. “forceUpdate” is a very heavy hammer for the following situation. Eventually, we’d like to make it smarter so that if there is a filter that’s time based, Corona knows to update, but for now, we’re pushing the responsibility to you all
The other mode that’s interesting is “wireframe”. It’s very similar to the physics debug draw modes, which we’re also considering adding as parameters, but we haven’t decided if they are orthogonal to these draw modes yet.
Does it matter where this is used (e.g. as the app starts, in enterframe…etc.)? And is it a one-time setting?
Thanks,
Dave
No, it’s a dynamic setting