| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0003436 | ParaView | (No Category) | public | 2006-06-23 15:11 | 2009-12-09 14:51 | ||||
| Reporter | Ken Moreland | ||||||||
| Assigned To | Dave DeMarle | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0003436: SNL: D3 strips global Ids | ||||||||
| Description | When running D3 on an input with global ids in it (for example read from an Exodus file), the global point and cell ids are stripped. D3 should have the opposite behavior. It should keep global ids if they are there or provide the global ids that it generates if they are not in the input. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0005525) user521 2006-10-24 15:55 |
See also bug 3782. Now that D3 uses vtkIdType internally the global ids are preserved. For instance I open can.ex2 and run it through D3. When I pick cell number 427 from either the reader or the filter the same cell is now picked in either case. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2009-12-09 14:51 | Berk Geveci | Project | @3@ => ParaView |
| 2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |