Better names for representations in Python trace
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Right now the Python trace is assigning names to representations that do not accurately reflect the source the representation is for. For example, if I make a simple trace of creating a sphere source and applying, I get a trace with the following:
Sphere1 = Sphere()
RenderView1 = GetRenderView() DataRepresentation1 = Show()
Rather than use the variable DataRepresentation1, we should be using something like Sphere1Representation1.