View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0013628ParaView(No Category)public2012-11-07 22:222016-08-12 09:59
ReporterAlan Scott 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version3.98.0 
Target VersionFixed in Version 
Summary0013628: Allow Warp by Vector to warp components
DescriptionA user wants to warp not by the displacement vector, but rather the displacement in only one component (Dispacement X, for instance). Allow the Warp by Vector filter to warp by components.
TagsNo tags attached.
ProjectSandia
Topic Name
Typefeature
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to 0013627closedAlan Scott Add X, Y or Z option to Apply Displacements 

-  Notes
(0029668)
Ken Moreland (manager)
2012-11-08 00:02

Wouldn't that just be a warp by scalar?
(0029675)
Alan Scott (manager)
2012-11-08 12:43

At it's most simple, no. Warp by scalar is not vector aware, thus won't allow a user to warp by one of the three coordinates. You could use the Calculator filter, but we need something more user friendly.
(0029679)
Ken Moreland (manager)
2012-11-08 13:10

Yes it (warp by scalar) can if you turn on the Auto Convert Properties option in settings.

I am pushing back on this request. I would prefer it not be done. Making this change would further obfuscate an already complicated interface. I realize this need is important, but it is also off the norm. I think it is ok to ask a user with a kinda weird need to make more clicks to set up the vis.
(0029683)
Alan Scott (manager)
2012-11-08 13:47

Now Ken, that is NOT (as in NOT) intuitive. It needs to be a great deal simpler than that. Maybe we always "auto convert" vectors to components, or add a check box on the filter?

I do agree that we don't want to just make filters more complex. But, it has to be somewhat obvious how to get things to work...
(0029684)
Ken Moreland (manager)
2012-11-08 14:18

I didn't say it was intuitive. I said you could do it and it wasn't that hard. You can set up this one (or small number of) user and problem solved.

I'm not against having auto convert properties on by default. Not totally sure why it isn't. The one downside I see is that it fills the chooser boxes with many more entries.
(0038275)
Kitware Robot (administrator)
2016-08-12 09:59

Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.

- Issue History
Date Modified Username Field Change
2012-11-07 22:22 Alan Scott New Issue
2012-11-07 22:25 Alan Scott Description Updated View Revisions
2012-11-08 00:02 Ken Moreland Note Added: 0029668
2012-11-08 12:43 Alan Scott Note Added: 0029675
2012-11-08 13:10 Ken Moreland Note Added: 0029679
2012-11-08 13:47 Alan Scott Note Added: 0029683
2012-11-08 14:18 Ken Moreland Note Added: 0029684
2016-07-13 21:55 Alan Scott Relationship added related to 0013627
2016-08-12 09:59 Kitware Robot Note Added: 0038275
2016-08-12 09:59 Kitware Robot Status backlog => closed
2016-08-12 09:59 Kitware Robot Resolution open => moved
2016-08-12 09:59 Kitware Robot Assigned To => Kitware Robot


Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker