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

Geometry.dispose() bugfix. #53

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

david-gregory
Copy link
Contributor

Was trying to remove SubGeometry twice from Vector (a shift and a splice (in removeSubGeometry)). This has been fixed now. (shift removed).

david-gregory and others added 16 commits May 25, 2011 09:01
This was originally added by Rob, but after discussing with him it was
concluded that because the Loader3D could essentially load anything, the
handle property does not really have a place anymore.
Loader3D would previously add containers that had been loaded even though they
already were parented (assumingly to something else in the file.) This commit
fixes this bug using a more general-purpose approach to adding scene assets to
the Loader3D as they come in.
Because the token always has a listener, the check for hasEventListener() was
always true and errors were never thrown. Copied this check out into Loader3D
so that errors are thrown when a load error occurrs and there is no LOAD_ERROR
listener on the Loader3D instance.
Because asset loader would only check whether a parsing had COMPLETED to decide
whether to resume or not, it would sometimes try to resume failed parsings. To
avoid this, it now checks for parsingPaused instead of !parsingComplete.
Using short for numJoints in a skeleton block, instead of 32-bit int which
was previuosly the case.
MichaelPlank pushed a commit to Pro3Games/away3d-core-broomstick that referenced this pull request Sep 20, 2011
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.

2 participants