View Issue Details

IDProjectCategoryView StatusLast Update
0027473CommunityOCCT:Visualizationpublic2016-12-09 16:38
ReporterVico Liang Assigned Tobugmaster  
PrioritynormalSeverityfeature 
Status closedResolutionfixed 
Target Version7.1.0Fixed in Version7.1.0 
Summary0027473: Expose Detected Point information in class SelectMgr_ViewerSelector
DescriptionSelectMgr_ViewerSelector has function DetectedEntity() to access Detected Entity. In practice, the detected point which can be calculated from the Depth is also useful. The detected point might be available in point selection mode.
TagsNo tags attached.
Test case numberNot needed

Activities

Vico Liang

2016-05-06 08:45

developer   ~0053875

Dear kgv,

Do you think it's reasonable to expose SelectMgr_SortCriterion which is associated with detected entity SelectBasics_SensitiveEntity and then add detected point value to SelectMgr_SortCriterion?

Vico Liang

2016-05-06 08:53

developer   ~0053876

I see there is a function VState in TKViewerTest project to get the detected point. But it is too complex to understand and also it's not an efficient way to get the detected point.

kgv

2016-05-06 15:07

developer   ~0053892

Last edited: 2016-05-06 15:07

Dear Vico,

I agree that method returning the coordinates of detected point would be useful for many applications - to avoid going deeper in details as done in vstate command.

> Do you think it's reasonable to expose SelectMgr_SortCriterion which is associated with detected entity SelectBasics_SensitiveEntity and then add detected point value to SelectMgr_SortCriterion?
SelectMgr_SortCriterion might be a reasonable place for holding coordinates as well, but in most cases depth value should sufficient for computing point.
So it is more about how to provide result at high-level API.

Vico Liang

2016-05-08 13:11

developer   ~0053911

Dear kgv,

Calculating the coordinates of detected point needs SelectMgr_SelectingVolumeManager and depth value. For different SensitiveEntity, the SelectMgr_SelectingVolumeManager might be transformed or scaled, so Depth value might be not sufficient.

kgv

2016-09-23 15:52

developer   ~0058084

Dear bugmaster,

please switch this bug to VERIFIED - the feature has been integrated in scope of patch for #0027834.

Issue History

Date Modified Username Field Change
2016-05-06 08:37 Vico Liang New Issue
2016-05-06 08:37 Vico Liang Assigned To => kgv
2016-05-06 08:45 Vico Liang Note Added: 0053875
2016-05-06 08:53 Vico Liang Note Added: 0053876
2016-05-06 15:07 kgv Note Added: 0053892
2016-05-06 15:07 kgv Note Edited: 0053892
2016-05-08 13:11 Vico Liang Note Added: 0053911
2016-09-23 15:52 kgv Note Added: 0058084
2016-09-23 15:52 kgv Assigned To kgv => bugmaster
2016-09-23 15:52 kgv Status new => feedback
2016-09-23 15:52 kgv Resolution open => fixed
2016-09-23 15:52 kgv Product Version 6.9.1 =>
2016-09-27 14:27 bugmaster Status feedback => tested
2016-09-27 14:27 bugmaster Status tested => assigned
2016-10-13 16:34 kgv Status assigned => feedback
2016-10-25 20:11 apn Test case number => Not needed
2016-10-25 20:11 apn Status feedback => tested
2016-10-25 20:11 apn Status tested => verified
2016-12-09 16:30 aiv Status verified => closed
2016-12-09 16:38 aiv Fixed in Version => 7.1.0