Display points and surfaces of polydata

[jaswantp (Jaswant Panchumarti (Kitware))]

@Julien_Champagnol

I also get the problem with other meshes, I’ve tried logging the point size that I just set and I get a correct programmatic output, but no correct behavior…

Okay, here’s a strange suggestion:

actor.GetProperty().EdgeVisibilityOn();
actor.GetProperty().VertexVisibilityOn();
actor.GetProperty().SetPointSize(10);

If that works, my hunch is right. I’ve always thought there was a bug where the opengl polydata mapper only respected the vertex visibility setting when edge visibility is switched on. Let me know what you see. I think this is an easy fix.

@Julien_Champagnol

Also what do you mean by old version of vtk? I’m using 9.3.1 which is 4 months old?

VTK 9.4 was just released a few days ago but it’s release candidates have been out for some weeks now, so I thought you were testing those wheels. One of the features in that that is you can access member variables without using the Set/Get functions.

VTK 9.4.0 Release

VTK Release Plan Starting with v9.4.0, VTK will follow a regular (calendar-based) release plan. Expect a minor release every 6 months with intermediate patch releases in between, as needed. Depending on the features added to the release, the release may become a major release. The master and release branches will split one month before the scheduled release date. Please ensure that all feature branches are merged before the split. A proposed detailed release plan will be announced a few weeks …