-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing a Data URI to Texture constructor hangs Loader (and isLoaded() never returns true) #1543
Comments
Good find, that shouldn't happen |
I believe the fix might be adding |
My suggested fix does not, in fact, resolve the hanging loader problem. |
I wonder if it's a missing promise resolve() that should fire when a data
URI is passed
…On Wed, May 13, 2020 at 10:34 AM Thomer Gil ***@***.***> wrote:
My suggested fix does not, in fact, resolve the hanging loader problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1543 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEVNZYSOHYO5MZITYLKWCDRRK4ZPANCNFSM4M7H7RZQ>
.
|
Awesome. |
If I'm reading the
Texture
constructor correctly, it should be able to handle Data URI aspath
. However, this hangs the loader forever.Invoking
.load()
on aTexture
object that was constructed with a Data URI never returnstrue
for.isLoaded()
.One thing that catches my attention in
Texture
's constructor is that it appears that:...is called for
path
that is not a Data URI, but it is never called for apath
that is a Data URI. See https://github.com/excaliburjs/Excalibur/blob/57e03f4d/src/engine/Resources/Texture.ts#L73The text was updated successfully, but these errors were encountered: