Painter can report wrong bounds on first check
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
When the Renderer first calls ComputeVisiblePropBounds, the poly data painter mapper calls ComputeBounds on its painter, but this happens the first time before setInput has been called on the painter. This patch fixes it.