You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't remember what it has to do with costume loading--in general, I'm not really happy with the whole "costumes pop into existence when they're loaded" way things currently work in Leopard. I'd prefer if there was some sort of "preload" function that you called before running a project that loaded all the costumes and sounds.
@towerofnix wrote:
I'm not as experienced with Leopard or Scratch or the differences between them, but I definitely got the same feeling while reviewing your code. Maybe you could open an issue suggesting a "preload" mechanic? I feel like proper support for that (alongside a "progress bar" for asset loading etc) would be pretty reasonable/good.
And thanks for the links!
The text was updated successfully, but these errors were encountered:
I think whatever we build should give the user considerable control over the loading screen. Ideally Leopard would provide a built-in loading screen that is simple and effective, and customizable to a degree (colors/text/etc). And perhaps also an escape hatch that allows rendering anything you want to the canvas based on the current loading state.
I think a Costume.load / Sound.load API that returns a Promise<Costume | Sound> could work. If we need more granular loading progress, we could emit progress events from Costume/Sound?
For now labelled as "discussion" as this may be a significant change from Leopard currently works! See discussion in #119 (comment):
The text was updated successfully, but these errors were encountered: