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 VTK compatibility #1056

Merged
merged 1 commit into from
Dec 23, 2014
Merged

Fix VTK compatibility #1056

merged 1 commit into from
Dec 23, 2014

Conversation

VictorLamoine
Copy link
Contributor

fran6co@4d1ee47#diff-4206b5bbfa76680243fec88c91dfbd3cL119 removed the update call which is in fact needed for VTK 5. It does not hurt VTK 6 support.

Reported by Ber461 on the mailing list.

jspricke added a commit that referenced this pull request Dec 23, 2014
@jspricke jspricke merged commit e1bfafc into PointCloudLibrary:master Dec 23, 2014
@VictorLamoine VictorLamoine deleted the tesselated_sphere branch January 2, 2015 13:37
@fran6co
Copy link
Contributor

fran6co commented Jan 6, 2015

It's not working for me for VTK 6.1.1:

/tmp/pcl-PsVzgR/apps/src/render_views_tesselated_sphere.cpp:123:11: error: no member named 'Update' in 'vtkPolyData'
  sphere->Update ();

@VictorLamoine
Copy link
Contributor Author

From what I remember I tested with VTK 6.1 release. If that doesn't work for you add a VTK version condition.

@fran6co fran6co mentioned this pull request Jan 6, 2015
@andoum
Copy link

andoum commented Jan 9, 2015

It seems like in VTK 6.1.0 the code bellow is still required
subdivide->Update();
Otherwise I get an empty sphere and segfault because there are no cam_positions.

@taketwo
Copy link
Member

taketwo commented Jan 9, 2015

Could you submit a pull request with refined #if condition?

@VictorLamoine
Copy link
Contributor Author

Aha! I was (partially) right 😃 These changes in VTK are annoying!

@fran6co
Copy link
Contributor

fran6co commented Jan 9, 2015

Yes, they are. Would be nice to have some middle layer to abstract this stuff or move away from vtk5. It would be nice to remove all this #ifdefs

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.

5 participants