OpenGLVMobject fix data alignment to support interpolating families #2737
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Overview: What does this pull request change?
This pull request extends
.OpenGLVMobject.pointwise_become_partialto improve stroke rendering #2714with fixing data alignment which then fixes some interpolation issues with families. The main problem is that the code in OpenGLMobject
align_dataon the first look serves the same purpose as the code in Mobject but the problem is that thenull_point_alignmentis missing.This PR adds back the nullpoint alignment but with integrating it in to the current structure of OpenGLMobject because it is more modern and should probably be ported over to Mobject at some point.
Adding
null_point_aligntoOpenGLMobjectAdding
null_point_align_familytoOpenGLMobjectMotivation and Explanation: Why and how do your changes improve the library?
Further improving the render capabilities of the OpenGL Renderer and the shrinking the difference in the output of the gl and cairo renderer
Bench.mp4
Cairo result to be aspired
Bench.mp4
Further Information and Comments
There still seems to be a problem with the other data alignments because the opacity on a transition is still somehow missing from somewhere.
Bench.mp4
Maybe this can be fixed in a future PR
Reviewer Checklist