MantisBT
Mantis Bug Tracker Workflow

View Revisions: Issue #27731 All Revisions ] Back to Issue ]
Summary 0027731: Visualization, OpenGl_AspectMarker - handle fractional marker Scale when sharing resources
Revision 2016-08-01 17:00 by kgv
Description Current code of OpenGl_AspectMarker::Resources::SpriteKeys() rounds the marker scale to the nearest integer number. However, some markers support fractional ratios (with step 0.5) leading to non-equal resources collision.

This is reflected by continuous regressions of test case bugs/vis/bug23654_MarkersRecompute - the second image is unstable. It is because on second display (Graphic3d_CView::Activate() after creating a new view) the order of displayed markers is undefined (Graphic3d_StructureManager::myDisplayedStructure is NCollection_Map<Handle(Graphic3d_Structure)>) and thus, collided marker resources are initialized in arbitrary order.
Revision 2016-08-01 15:41 by kgv
Description Current code of OpenGl_AspectMarker::Resources::SpriteKeys() rounds the marker scale to the nearest integer number. However, some markers support fractional ratios (with step 0.5) leading to non-equal resources collision.

This is reflected by continuous regressions of test case bugs/vis/bug23654_MarkersRecompute - the second image is unstable. It is because on second display the order of displayed markers is undefined (Graphic3d_CView::myStructsDisplayed is NCollection_Map<Handle(Graphic3d_Structure)>) and thus, collided marker resources are initialized in arbitrary order.


Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker