View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012941ParaView(No Category)public2012-02-15 14:452012-02-20 10:28
ReporterSankhesh Jhaveri 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version3.14 
Summary0012941: Properties tab shows properties of output port 0 only
DescriptionIf a reader/filter has multiple output ports and you try to connect another filter to any output port other than output port 0, the pipeline gets connected to the correct output port but the properties tab allows changing properties based on output port 0 only.

To reproduce,
1. Tools->Manage Plugins->SLACTools->Load Selected
2. File->Open->ParaViewData/SLAC/pic-example/mesh.ncdf
3. Select SLAC mesh from the dialog
4. In Properties tab, check all the first two checkboxes.
5. Apply
6. Observe in the Information tab, the first output(External Surface) has 6 blocks in the multiblock dataset and second output(Entire volume) has 4.
7. Select Entire Volume.
8. Filters->Alphabetical->ExtractBlock

Observe that in the Properties tab of Extract Block, where we need to select which blocks to extract, it shows 6 blocks that belong to the first output(External Surface) whereas the ExtractBlock filter is connected to the second output port.
TagsNo tags attached.
ProjectTBD
Topic Name12941_fix_multiple_output_ports
Typeincorrect functionality
Attached Filespng file icon Screenshot at 2012-02-15 14:40:10.png [^] (159,424 bytes) 2012-02-15 14:46

 Relationships

  Notes
(0028269)
Utkarsh Ayachit (administrator)
2012-02-15 23:16

commit 44ac95a6c99668a5041c7c50f19ba7123f1186c9
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Wed Feb 15 23:14:33 2012 -0500

    BUG 0012941. Fixed handling of multiple output ports.
    
    All domains were ending up using port 0 even when the filter was connected to an
    output port > 0. The problem was because the unchecked state wasn't updated
    correctly on vtkSMInputProperty (as was done for other properties). Fixed that.
(0028290)
Utkarsh Ayachit (administrator)
2012-02-17 12:22

Merged into git-master, if applicable.
(0028295)
Sankhesh Jhaveri (developer)
2012-02-17 14:16

Solved. Nice.

 Issue History
Date Modified Username Field Change
2012-02-15 14:45 Sankhesh Jhaveri New Issue
2012-02-15 14:46 Sankhesh Jhaveri File Added: Screenshot at 2012-02-15 14:40:10.png
2012-02-15 23:16 Utkarsh Ayachit Topic Name => 12941_fix_multiple_output_ports
2012-02-15 23:16 Utkarsh Ayachit Note Added: 0028269
2012-02-15 23:16 Utkarsh Ayachit Status backlog => gatekeeper review
2012-02-15 23:16 Utkarsh Ayachit Fixed in Version => git-next
2012-02-15 23:16 Utkarsh Ayachit Resolution open => fixed
2012-02-15 23:16 Utkarsh Ayachit Assigned To => Utkarsh Ayachit
2012-02-17 12:22 Utkarsh Ayachit Fixed in Version git-next => git-master
2012-02-17 12:22 Utkarsh Ayachit Status gatekeeper review => customer review
2012-02-17 12:22 Utkarsh Ayachit Note Added: 0028290
2012-02-17 14:16 Sankhesh Jhaveri Note Added: 0028295
2012-02-17 14:16 Sankhesh Jhaveri Status customer review => closed
2012-02-20 10:28 Utkarsh Ayachit Fixed in Version git-master => 3.14


Copyright © 2000 - 2018 MantisBT Team