View Issue Details

IDProjectCategoryView StatusLast Update
0026791Open CASCADEOCCT:Visualizationpublic2022-10-19 15:49
Reporterkgv Assigned Tovpozdyayev  
PrioritylowSeverityfeature 
Status assignedResolutionopen 
Target Version7.8.0 
Summary0026791: Visualization, TKOpenGl - apply view resolution to built-in markers
DescriptionStandard markers can be automatically computed with greater resolution on HiDPI monitors.
Steps To Reproducebugs vis bug26791
TagsNo tags attached.
Test case number

Attached Files

  • bug24131_markers_sprites.png (32,728 bytes)

Relationships

related to 0031705 closedbugmaster Open CASCADE Visualization - move out construction of predefined markers from OpenGl_AspectsSprite to Graphic3d_MarkerImage 
related to 0027731 closedbugmaster Open CASCADE Visualization, OpenGl_AspectMarker - handle fractional marker Scale when sharing resources 
child of 0025350 closedbugmaster Community Visualization - provide a dpi-scaling ratio for V3d_View 

Activities

git

2015-11-11 10:47

administrator   ~0048042

Branch CR26791 has been created by isk.

SHA-1: b9b37c1d45a06c976b593971fa1f05143c930bc6


Detailed log of new commits:

Author: isk
Date: Wed Nov 11 10:46:48 2015 +0300

    0026791: Visualization, TKOpenGl - apply view resolution to built-in markers
    Add ResolutionRatio() method in the Graphic3d_RenderingParams.
    Add SetResolutionRatio() method in the OpenGl_Context.

isk

2015-11-11 10:48

developer   ~0048043

Dear Kirill,
please review the branch CR26791.

kgv

2015-11-11 11:02

developer  

bug24131_markers_sprites.png (32,728 bytes)

kgv

2015-11-11 11:05

developer   ~0048046

Last edited: 2015-11-11 11:06

Please note that increasing resolution should have another effect that currently provided by changing marker size. It should be rendered with higher quality (e.g. with more pixels) preserving original shape at the same size (size from aspect).

For instance, lines within marker should have higher thickness (better within integer steps).

At the same time, the resolution should have no effect on custom markers - them should be rendered as is.

Issue History

Date Modified Username Field Change
2015-10-21 09:25 kgv New Issue
2015-10-21 09:25 kgv Assigned To => kgv
2015-10-21 09:25 kgv Relationship added child of 0025350
2015-10-21 09:26 kgv Assigned To kgv => isk
2015-10-21 09:26 kgv Status new => assigned
2015-10-21 09:26 kgv Target Version 7.0.0 => 7.1.0
2015-11-11 10:47 git Note Added: 0048042
2015-11-11 10:48 isk Note Added: 0048043
2015-11-11 10:48 isk Assigned To isk => kgv
2015-11-11 10:48 isk Status assigned => resolved
2015-11-11 10:48 isk Steps to Reproduce Updated
2015-11-11 11:02 kgv File Added: bug24131_markers_sprites.png
2015-11-11 11:05 kgv Note Added: 0048046
2015-11-11 11:05 kgv Assigned To kgv => isk
2015-11-11 11:05 kgv Status resolved => assigned
2015-11-11 11:06 kgv Note Edited: 0048046
2016-08-06 13:04 kgv Relationship added related to 0027731
2016-08-06 13:04 kgv Assigned To isk => kgv
2016-08-06 13:04 kgv Priority normal => low
2016-10-25 09:33 kgv Target Version 7.1.0 => 7.2.0
2017-07-20 10:50 kgv Target Version 7.2.0 => 7.4.0
2019-08-13 12:04 kgv Target Version 7.4.0 => 7.5.0
2020-08-28 16:31 kgv Target Version 7.5.0 => 7.6.0
2020-12-14 17:15 kgv Relationship added related to 0031705
2021-08-24 14:26 kgv Target Version 7.6.0 => 7.7.0
2022-08-17 11:57 kgv Target Version 7.7.0 => 7.8.0
2022-10-19 15:49 smoskvin Assigned To kgv => vpozdyayev