View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0030641 | Open CASCADE | OCCT:Visualization | public | 2019-04-09 11:35 | 2019-10-23 16:56 |
Reporter | nds | Assigned To | bugmaster | ||
Priority | normal | Severity | feature | ||
Status | closed | Resolution | no change required | ||
Product Version | 7.4.0 | ||||
Target Version | 7.4.0 | ||||
Summary | 0030641: Visualization - possibility to select in predefined ZLayers only | ||||
Description | The reason of proposed improvement: - the viewer scene contains objects in several layers (layer of usual 3D objects and several layers with objects used 2D persistent), - there are a lot of objects displayed in default ZLayer, - some of application algorithm requires selection of objects in only one of layers(e.g. in 2D layer). | ||||
Tags | No tags attached. | ||||
Test case number | Not needed | ||||
|
One of possible solution is to Deactivate/Activate not necessary objects, but it seems that (as there are a lot of objects) it breaks performance. So, is it possible to provide an interface to deactivate temporary some of ZLayers in selection mechanism of Visualization? |
|
It looks clumsy introducing extra means of ZLayers deactivation/activation in selection. Selection restrictions are usually done via selection filters (AIS_InteractiveContext::AddFilter()). The performance of Deactivation/Activation is another issue. One of possible improvements is splitting selection entities into dedicated BVH trees per Z-Layer, which would be consistent to how TKOpenGl already manages presentations. So that adding/removing selectable object into auxiliary Z layer would not be slow in case of a large scene. |
|
Branch CR30641 has been created by nds. SHA-1: 6e940e66ffe4746f50d088289c0104a2724e89ea Detailed log of new commits: Author: nds Date: Tue Apr 9 12:00:28 2019 +0300 0030641: Visualization - possibility to select in predefined ZLayers only |
|
Dear Kirill, please have a look at CR30641. Best regards, Natalia |
|
Dear bugmaster, please close this issue. The reason is that the expected problem with performance has not been discovered in checked cases even without modifications prepared for this issue. |
|
Branch CR30641 has been deleted by kgv. SHA-1: 6e940e66ffe4746f50d088289c0104a2724e89ea |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-04-09 11:35 | nds | New Issue | |
2019-04-09 11:35 | nds | Assigned To | => kgv |
2019-04-09 11:36 | nds | Note Added: 0083553 | |
2019-04-09 11:49 | kgv | Note Added: 0083555 | |
2019-04-09 11:49 | kgv | Note Edited: 0083555 | |
2019-04-09 11:49 | kgv | Note Edited: 0083555 | |
2019-04-09 12:07 | git | Note Added: 0083557 | |
2019-04-09 12:10 | nds | Note Added: 0083558 | |
2019-04-09 12:21 | kgv | Assigned To | kgv => nds |
2019-04-09 12:21 | kgv | Status | new => feedback |
2019-04-09 13:35 | kgv | Relationship added | related to 0028638 |
2019-09-04 18:11 | nds | Note Added: 0086745 | |
2019-09-04 18:11 | nds | Assigned To | nds => bugmaster |
2019-09-25 07:50 | bugmaster | Status | feedback => closed |
2019-09-25 07:50 | bugmaster | Resolution | open => no change required |
2019-10-23 11:54 | git | Note Added: 0088490 | |
2019-10-23 16:56 | apn | Test case number | => Not needed |