View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0027396 | Community | OCCT:Coding | public | 2016-04-16 10:15 | 2017-10-06 14:41 |
| Reporter | eryar | Assigned To | |||
| Priority | low | Severity | integration request | ||
| Status | closed | Resolution | won't fix | ||
| Platform | Windows | OS | VC++ 2013 | ||
| Product Version | 7.0.0 | ||||
| Summary | 0027396: TopLoc in TKMath Toolkit | ||||
| Description | TopLoc is used to define Shape Location, I think this package should belong to the TKBRep Toolkit. | ||||
| Tags | No tags attached. | ||||
| Test case number | Not required | ||||
| child of | 0008682 | closed | Open CASCADE | General revision of OCCT packaging |
|
|
I agree with eryar. TopLoc is mainly used for BREP Shape, it should be better to move it to TKBRep. |
|
|
TopLoc_Location is a general class defining sequence of transformations. It's definition is not specific to BRep shape. For me, the current location of this package in TKMath toolkit look logical. Although TopLoc_Location is mostly used within TopoDS_Shape, it is not limited to it. For instance, it has been used for defining transformations within AIS classes (not only for TopoDS_Shape presentations). Anyway, I don't see how moving TopLoc package to another toolkit might be useful to anyone. |
|
|
Yes. Moving TopLoc package to another toolkit maybe not useful to anyone. But from the name of the package TopLoc and the document about TopLoc is also in the user guide: Modeling Data, not in Foundation Classes. |
|
|
TopLoc has been moved from TKBRep to TKMath in context of 0008682, with a view to allow separation of basic visualization services (PrsMgr, Select3D, SelectMgr) from toolkits implementing BREP data structures and algorithms. See report attached to 0008682 for explanation. This is probably not relevant any more and can be revised. |
|
|
Closing this issue as it seems to be not worth implementing (there are no benefit of moving, but it can harm some existing code that may rely on current situation). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-16 10:15 | eryar | New Issue | |
| 2016-04-16 10:15 | eryar | Assigned To | => kgv |
| 2016-04-17 10:08 | Vico Liang | Note Added: 0052763 | |
| 2016-04-17 10:46 | kgv | Note Added: 0052764 | |
| 2016-04-17 10:46 | kgv | Assigned To | kgv => abv |
| 2016-04-17 10:46 | kgv | Priority | normal => low |
| 2016-04-17 10:46 | kgv | Severity | minor => integration request |
| 2016-04-18 15:08 | eryar | Note Added: 0053268 | |
| 2016-04-18 16:58 |
|
Relationship added | child of 0008682 |
| 2016-04-18 17:02 |
|
Note Added: 0053272 | |
| 2017-08-15 14:32 |
|
Test case number | => Not required |
| 2017-10-06 14:41 |
|
Note Added: 0071263 | |
| 2017-10-06 14:41 |
|
Status | new => closed |
| 2017-10-06 14:41 |
|
Resolution | open => won't fix |
