MantisBT - ParaView |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0014667 | ParaView | (No Category) | public | 2014-04-07 15:49 | 2014-08-29 10:59 |
|
| Reporter | Ken Moreland | |
| Assigned To | Utkarsh Ayachit | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 4.1 | |
| Target Version | 4.2 | Fixed in Version | 4.2 | |
| Project | TBD |
| Topic Name | |
| Type | incorrect functionality |
|
| Summary | 0014667: One transparent block makes all blocks non-selectable in 3D view |
| Description | One problem with the new feature of independently changing view properties on multiblock data sets is that if you make one block transparent, the entire data set becomes inaccessible to right clicks and selections in the 3D view. Generally we have disabled 3D view selection of transparent objects, but you should still be able to select the opaque parts of a multiblock data set.
To replicate, do the following:
1. Open can.ex2. Apply.
2. Change the view to see both the brick and the can.
3. Right click on the brick. In the pop-up window, select Set Block Opacity.
4. Change the opacity to something lower than 1 (e.g. 0.5).
5. Right click on the can. You don't get the pop-up menu for that object/block.
6. Try to do a select cells on surface anywhere on the can. You cannot do so.
|
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  multiblock.vtm (394) 2014-04-24 20:01
https://www.vtk.org/Bug/file/9645/multiblock.vtm |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2014-04-07 15:49 | Ken Moreland | New Issue | |
| 2014-04-24 20:01 | Adam Brown | File Added: multiblock.vtm | |
| 2014-04-24 20:02 | Adam Brown | Note Added: 0032606 | |
| 2014-04-24 20:47 | Adam Brown | Note Added: 0032607 | |
| 2014-06-09 07:30 | Utkarsh Ayachit | Note Added: 0032796 | |
| 2014-06-09 07:31 | Utkarsh Ayachit | Target Version | => 4.2 |
| 2014-06-17 09:02 | Utkarsh Ayachit | Note Added: 0032879 | |
| 2014-06-17 09:02 | Utkarsh Ayachit | Status | backlog => gatekeeper review |
| 2014-06-17 09:02 | Utkarsh Ayachit | Fixed in Version | => git-master |
| 2014-06-17 09:02 | Utkarsh Ayachit | Resolution | open => fixed |
| 2014-06-17 09:02 | Utkarsh Ayachit | Assigned To | => Utkarsh Ayachit |
| 2014-06-17 09:02 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
| 2014-06-26 21:59 | Alan Scott | Note Added: 0032931 | |
| 2014-06-26 21:59 | Alan Scott | Status | customer review => closed |
| 2014-08-29 10:59 | Utkarsh Ayachit | Fixed in Version | git-master => 4.2 |
|
Notes |
|
|
(0032606)
|
|
Adam Brown
|
|
2014-04-24 20:02
|
|
I can also confirm this problem with ParaView 4.1.
1. Load a multi-block file (sample attached)
2. Right click on one block and change the opacity using the context menu
or
Change the opacity value in the Colouring panel under the Properties tab
(this is recoverable)
3. The context menu is now disabled
4. Block selection is also disabled |
|
|
|
(0032607)
|
|
Adam Brown
|
|
2014-04-24 20:47
|
|
|
note that the Multi-block inspector can be used as a reasonable work around until this is fixed. You can still select blocks and set their visibility properties via the inspector even when some blocks are transparent. |
|
|
|
(0032796)
|
|
Utkarsh Ayachit
|
|
2014-06-09 07:30
|
|
|
This is related to BUG 0014412. I think it should already have been resolved -- need to verify. |
|
|
|
(0032879)
|
|
Utkarsh Ayachit
|
|
2014-06-17 09:02
|
|
|
Verified that this now works in git/master. |
|
|
|
(0032931)
|
|
Alan Scott
|
|
2014-06-26 21:59
|
|
|
Tested remote server, master, Linux. |
|