View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0009368ParaViewFeaturepublic2009-08-05 14:272016-08-12 09:57
ReporterDave DeMarle 
Assigned ToKitware Robot 
PrioritylowSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product VersionDevelopment 
Target VersionFixed in Version 
Summary0009368: Usability: key for icons
DescriptionCan we have a key for icons? For instance, open an exodus file, what do all the different icons for available arrays mean? For example field data, side sets etc. Is there some place one can go to look them up, besides looking in source tree, then grepping for icon filename in code etc.
TagsNo tags attached.
Topic Name
Attached Files


Ken Moreland (manager)
2009-08-05 14:35

We talked about some of this way back when we were first designing the ParaView 3 interface. In particular, we considered the idea of having multiple eyeballs for each entry in the pipeline browser. In the end we discounted this idea because there is no good way to associate which eyeball goes to which view. In essence, the result is worse than what we have because we go from an interface that encourages mistakes through inattention to one that encourages mistakes through confusion.

Placing icons in the browser that give cues to which view is active sounds fine, but I'm not sure how effective this would be, especially when you have multiple views of the same type.
Dave DeMarle (administrator)
2009-08-05 15:19

I think the note was meant for issue 0009366. So I am duplicating it there. This bug just mentions the need for some way to figure out what the various icons mean. Tooltips would be sufficient for the purpose, or a key in the help listing all icons and their known meanings.
Ken Moreland (manager)
2009-08-05 20:14

Oops. So I did. Thanks for the correction.
Utkarsh Ayachit (administrator)
2011-02-18 13:54
edited on: 2011-02-18 13:54

Probably just tooltips for those icons would make life easier.

Kitware Robot (administrator)
2016-08-12 09:57

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
2009-08-05 14:27 Dave DeMarle New Issue
2009-08-05 14:35 Ken Moreland Note Added: 0017068
2009-08-05 15:19 Dave DeMarle Note Added: 0017070
2009-08-05 20:14 Ken Moreland Note Added: 0017074
2011-02-18 13:54 Utkarsh Ayachit Note Added: 0025488
2011-02-18 13:54 Utkarsh Ayachit Note Edited: 0025488
2011-02-18 13:54 Utkarsh Ayachit Target Version => 4.0
2011-02-18 13:55 Utkarsh Ayachit Priority normal => low
2011-06-16 13:10 Zack Galbreath Category Feature Request => Feature
2016-08-12 09:57 Kitware Robot Note Added: 0037675
2016-08-12 09:57 Kitware Robot Status backlog => closed
2016-08-12 09:57 Kitware Robot Resolution open => moved
2016-08-12 09:57 Kitware Robot Assigned To => Kitware Robot

Copyright © 2000 - 2018 MantisBT Team