Skip to content
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

fix ImageLoader manager issue #9176

Merged
merged 2 commits into from
Jun 24, 2016
Merged

fix ImageLoader manager issue #9176

merged 2 commits into from
Jun 24, 2016

Conversation

indif
Copy link
Contributor

@indif indif commented Jun 20, 2016

The image won't complete until image.onload be called.

@mrdoob
Copy link
Owner

mrdoob commented Jun 20, 2016

Oh! Interesting... I think this is, in fact, a regression? 😐

@mrdoob mrdoob merged commit 35216e7 into mrdoob:dev Jun 24, 2016
@mrdoob
Copy link
Owner

mrdoob commented Jun 24, 2016

Thanks!

@mrdoob mrdoob mentioned this pull request Jul 10, 2016
@@ -26,7 +30,7 @@ Object.assign( THREE.ImageLoader.prototype, {

} else {

var loader = new THREE.XHRLoader( this.manager );
Copy link

@gabrielcramer gabrielcramer Sep 28, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove this.manager? In #9600 I put it back.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think because it would produce duplicates otherwise.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ImageLoader will call the methods itemStart and itemEnd of its loadingManager and the XHRLoader/FileLoader will call the same methods of a default loading Manager. I think it would be nice to let the FileLoader use the loading manager and this way we can store all active requests and abort them all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants