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
This is something I'm going to work on if I have the time.
Right now each loading block in Skins will pause until it's finished loading the skin. That's fine in circumstances where someone new to the extension might be confused why their blocks don't work, but in advanced cases where loading several skins in (sometimes hundreds) is necessary, the waiting can add up
As I understand it, there's no performance reason why it would need to wait.
My current plan is to add a block that'll enable/disable the "waiting", but I'm not settled on it yet.
The text was updated successfully, but these errors were encountered:
This is something I'm going to work on if I have the time.
Right now each loading block in Skins will pause until it's finished loading the skin. That's fine in circumstances where someone new to the extension might be confused why their blocks don't work, but in advanced cases where loading several skins in (sometimes hundreds) is necessary, the waiting can add up
As I understand it, there's no performance reason why it would need to wait.
My current plan is to add a block that'll enable/disable the "waiting", but I'm not settled on it yet.
Skins could be loaded concurrently (e.g. in a web worker) to avoid lag (if that's possible), but creators could also use loading screens so users don't notice.
This is something I'm going to work on if I have the time.
Right now each loading block in Skins will pause until it's finished loading the skin. That's fine in circumstances where someone new to the extension might be confused why their blocks don't work, but in advanced cases where loading several skins in (sometimes hundreds) is necessary, the waiting can add up
As I understand it, there's no performance reason why it would need to wait.
My current plan is to add a block that'll enable/disable the "waiting", but I'm not settled on it yet.
The text was updated successfully, but these errors were encountered: