| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0004295 | ParaView | (No Category) | public | 2007-01-10 13:00 | 2007-02-05 16:08 | ||||
| Reporter | Ken Moreland | ||||||||
| Assigned To | Mark Richardson | ||||||||
| Priority | urgent | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0004295: Select Input when filter deleted | ||||||||
| Description | Whenever any object is deleted in the pipeline browser, that object is necessarily selected in the pipeline browser. After the deletion, the selection changes to the first item in the browser: the server. That is never where I really want the selection to go. As a first guess, it would be better to select the input of the deleted filter (assuming there is only one input). More often then not, that is the object I want to modify next. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0006268) Mark Richardson (reporter) 2007-01-25 17:18 |
The selection is now changed when removing a pipeline object. The parent object is selected. If a source is deleted, the server is selected. If a filter with one input is deleted, the input is selected. If a filter with more than one input is deleted, the server is selected. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |