MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013583ParaView(No Category)public2012-10-29 08:102012-11-14 16:32
ReporterFelipe Bordeu 
Assigned ToSebastien Jourdain 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version3.14.1 
Target VersionFixed in Version 
ProjectTBD
Topic Name
Typeincorrect functionality
Summary0013583: Transform does not change the label data
DescriptionWhen a ShearedCube (plugin) is created with:

Use Base : enabled
Use Custom Range :enabled

and the a transform filter is applied with rotation, scale, translation. The cube Axes information is not transform.

to recreate this bug :

load plugin NonOrthogonalsource.
Sources -> ShearedCube
enable "Use Base" and "Use Custom Range"
Apply Transform filter (with any rotation/translation/scale)
In the Display tab, enable CubeAxes Visible

Felipe

Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng CustomCubeAxesTransformBug.png (135,251) 2012-10-29 08:10
https://www.vtk.org/Bug/file/9322/CustomCubeAxesTransformBug.png
png
Issue History
Date ModifiedUsernameFieldChange
2012-10-29 08:10Felipe BordeuNew Issue
2012-10-29 08:10Felipe BordeuFile Added: CustomCubeAxesTransformBug.png
2012-11-14 16:32Sebastien JourdainNote Added: 0029718
2012-11-14 16:32Sebastien JourdainStatusbacklog => closed
2012-11-14 16:32Sebastien JourdainAssigned To => Sebastien Jourdain
2012-11-14 16:32Sebastien JourdainResolutionopen => fixed

Notes
(0029718)
Sebastien Jourdain   
2012-11-14 16:32   
The annotation generated by the ShearedCube is not meant to be used by any filter other than the cube axis itself and therefore, if the geometry get changed in between the cube axes will still follow the directive provided as annotation without knowing the data has changed.

A fix would be to extend the vtkTransformFilter to perform transformation on those annotation, but regarding the usage of those annotation, I don't believe it is the right solution.

Instead a custom filter can be created at the end of the pipeline to create an oriented bounding box and then provide the proper annotation to the cube axis.

For now, I'll mark that bug closed as we won't fix it.