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

Fail to load SVG in P3D #3379

Closed
StanLepunK opened this Issue Jun 12, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@StanLepunK

StanLepunK commented Jun 12, 2015

Procesing 3.0a10, 3.0a9, 3.0a8
OSX 10.9 / iMac 2012

PShape pirate ;
void setup() {
  size(640,480, P3D) ;
  pirate = loadShape("pirate.svg") ;
}

Problem to load.
the consol return:
ClassCastException: processing.opengl.PGraphics3D cannot be cast to processing.opengl.PGraphics

for Processing 3.0a7

void draw() {
  shape(pirate, 0, 0, 100, 100); 
}

Problem to read
the consol return: NullPointerException

Work fine with file.obj, P2D and Processing 3.0a5.

@codeanticode The war versus openGL continue !

@codeanticode codeanticode self-assigned this Jun 12, 2015

@codeanticode codeanticode added the opengl label Jun 12, 2015

@codeanticode

This comment has been minimized.

Show comment
Hide comment
@codeanticode

codeanticode Jun 12, 2015

Member

Thanks for the report, will look into it.

Member

codeanticode commented Jun 12, 2015

Thanks for the report, will look into it.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jun 12, 2015

Member

@codeanticode This may be due to the changes I made to remove the several copies of loadShape() that were sprinkled around OpenGL.

Member

benfry commented Jun 12, 2015

@codeanticode This may be due to the changes I made to remove the several copies of loadShape() that were sprinkled around OpenGL.

@codeanticode

This comment has been minimized.

Show comment
Hide comment
@codeanticode

codeanticode Jun 12, 2015

Member

yes, thanks for the reminder. It is now fixed with f0f9558

Member

codeanticode commented Jun 12, 2015

yes, thanks for the reminder. It is now fixed with f0f9558

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment