Stencil API design

Issue #569 resolved
created an issue

setStencil and setInvertedStencil, when called without arguments, seem to do the same thing.

Perhaps setStencil could take a second argument which determines whether it is normal or inverted? This would eliminate the redudancy mentioned above, and there'd be one less function.

Another thing, newStencil doesn't seem to really do anything other than return the function it's given, which seems unnecessary and kind of makes stencils seem like objects. Maybe newStencil could be removed?

Comments (1)

  1. Log in to comment