Fragile features, make more reliable

[owmo-dev]

Right now capturing features can be a bit fragile, depending on how computationally expensive initial frame render can be. It can cause the delayed request for features on frontend to hang and not get result. This means that CSV capture may miss a feature occasionally when capturing sets.

Manual resolutions include:

• Reducing resolution
• Turning off animation
• Increasing capture time

It would be ideal to come up with a better solution than "just wait 600ms and try" - perhaps a loop that will continue to try iteratively until it succeeds? Maybe adding a callback of some kind that the artist can call at a specific time?

[owmo-dev]

Idea: having an event listener in the main app watch for a message similar to the provider's communication might be an easy way to get a message "out" of the iframe. Possibly just put an easy-to-use function in the provider script itself.

[owmo-dev]

On my latest project, they appear to be broken completely... maybe capturing 3-4 before stopping. CSV exports but it's missing a lot of data.

IDEA
Cache each entry to local storage and then at the end retrieve the results for the CSV. Probably better than holding them in memory, which may be getting lost for some reason.

https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Client-side_web_APIs/Client-side_storage