View Issue Details

IDProjectCategoryView StatusLast Update
0025741Open CASCADEOCCT:Modeling Datapublic2015-03-05 10:02
ReportermsvAssigned Tobugmaster  
PrioritynormalSeveritytext 
Status closedResolutionno change required 
Product Version6.9.0 
Target Version6.9.0 
Summary0025741: Specification of semantic of Closed flag of a shape
DescriptionThis issue is to update the user guide concerning the new semantic of Closed flag of a shape, which was made in the scope of the bug 0025656.
Steps To ReproduceNot applicable
TagsNo tags attached.
Test case number

Relationships

related to 0025656 closedbugmaster Specification of semantic of Closed flag of an edge 

Activities

git

2015-03-04 07:26

administrator   ~0038062

Branch CR25741 has been created by azv.

SHA-1: 9cad85d419de9d369eacf2afc97007c180daedb3


Detailed log of new commits:

Author: azv
Date: Wed Mar 4 07:25:36 2015 +0300

    0025741: Specification of semantic of Closed flag of a shape

azv

2015-03-04 07:28

administrator   ~0038063

Dear Mikhail,

A note about using of the "Closed" flag is added to the "BRep Format" user guide. Could you, please, review branch CR25741?

msv

2015-03-04 12:30

developer   ~0038070

I think the semantic of shape flags should not be described in the BRep format user guide. It describes only way of storage of shapes, not the meaning.
In other guides, there is no explicit statements about closed flag of an edge. Moreover, Modeling Data guide contains description of meaning of different shape types, and that description tells that wires and shells can be open or closed, and nothing about edge closeness.

So, I consider this bug must be closed.

msv

2015-03-04 12:31

developer   ~0038071

Dear bugmaster, please remove the branch CR25741.

msv

2015-03-04 12:32

developer   ~0038072

Please, close this bug

git

2015-03-05 10:02

administrator   ~0038118

Branch CR25741 has been deleted by inv.

SHA-1: 9cad85d419de9d369eacf2afc97007c180daedb3

bugmaster

2015-03-05 10:02

administrator   ~0038119

branch CR25741 was removed

Issue History

Date Modified Username Field Change
2015-01-22 17:02 msv New Issue
2015-01-22 17:02 msv Assigned To => azv
2015-01-22 17:02 msv Status new => assigned
2015-01-22 17:03 msv Relationship added related to 0025656
2015-03-04 07:26 git Note Added: 0038062
2015-03-04 07:28 azv Note Added: 0038063
2015-03-04 07:28 azv Assigned To azv => msv
2015-03-04 07:28 azv Status assigned => resolved
2015-03-04 07:28 azv Steps to Reproduce Updated
2015-03-04 12:30 msv Note Added: 0038070
2015-03-04 12:31 msv Note Added: 0038071
2015-03-04 12:32 msv Note Added: 0038072
2015-03-04 12:32 msv Assigned To msv => bugmaster
2015-03-04 12:32 msv Status resolved => reviewed
2015-03-05 10:02 git Note Added: 0038118
2015-03-05 10:02 bugmaster Note Added: 0038119
2015-03-05 10:02 bugmaster Status reviewed => closed
2015-03-05 10:02 bugmaster Resolution open => no change required