${taskforce.name} Avatar
  1. OMG Task Force

CAD Services 1.1 RTF — All Issues

  • Key: CAD11
  • Issues Count: 34
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
CAD11-34 interface Parameter CAD 1.0 CAD 1.1 Resolved closed
CAD11-28 Set color on Layer interface CAD 1.0 CAD 1.1 Resolved closed
CAD11-29 Operation to identify opened Models CAD 1.0 CAD 1.1 Resolved closed
CAD11-32 CadFoundation.idl: In the CadFoundation::EntityPropsStruct CAD 1.0 CAD 1.1 Resolved closed
CAD11-31 bounding_box" behavior CAD 1.0 CAD 1.1 Resolved closed
CAD11-30 Add operations to CadMain::Model CAD 1.0 CAD 1.1 Resolved closed
CAD11-33 struct PolyLineStruct is defined but not used anywhere CAD 1.0 CAD 1.1 Resolved closed
CAD11-24 "Entity-Types" CAD 1.0 CAD 1.1 Resolved closed
CAD11-25 "Cadsystem" interface issue CAD 1.0 CAD 1.1 Resolved closed
CAD11-26 interface Model : CadFoundation:: Attributable replaced CAD 1.0 CAD 1.1 Resolved closed
CAD11-27 remove CadGeometryExtens interface CAD 1.0 CAD 1.1 Resolved closed
CAD11-22 Tessellation Types CAD 1.0 CAD 1.1 Resolved closed
CAD11-23 Curve Parameters CAD 1.0 CAD 1.1 Resolved closed
CAD11-21 Euclidean Dimension CAD 1.0 CAD 1.1 Resolved closed
CAD11-17 Documentation for CadMain::Model::unique_entities() CAD 1.1 open
CAD11-19 Model Instances vs. Top-Level Entities CAD 1.0 CAD 1.1 Resolved closed
CAD11-18 Add some operations to CadFoundation module's interfaces CAD 1.0 CAD 1.1 Resolved closed
CAD11-20 EntityFactory and ModelInstanceFactory CAD 1.0 CAD 1.1 Resolved closed
CAD11-15 Data in CadGeometry::EdgeTessellationStuct CAD 1.1 open
CAD11-16 CadMain::Model interface issue CAD 1.1 open
CAD11-14 CADServices 1.1 issue CAD 1.1 open
CAD11-13 CadBrep::OrientedEdge interface issue CAD 1.1 open
CAD11-12 CadBrep module issue CAD 1.1 open
CAD11-11 method CadMain::Model::unique_ids_to_entities() CAD 1.1 open
CAD11-10 description for CadMain::Model::unique_ids_to_entities() is missing CAD 1.1 open
CAD11-8 return value of CadFoundation::Entity::cad_model() CAD 1.0 open
CAD11-6 CadFoundation::EntityPropsStruct CAD 1.0 open
CAD11-9 exception CadConnection::BadParameter does not match the method anymore CAD 1.1 open
CAD11-7 different tessellation structures for different kind of entities CAD 1.1 open
CAD11-5 Model creation parameters CAD 1.1 open
CAD11-2 struct HyperbolaStruct should be moved from CadSurface to CadCurve CAD 1.0 open
CAD11-4 File CadMain: Method add_child and remove_child CAD 1.0 open
CAD11-1 File CadGeometryExtens CAD 1.0 open
CAD11-3 struct OffsetCurveStruct CAD 1.0 open

Issues Descriptions

interface Parameter

  • Key: CAD11-34
  • Legacy Issue Number: 5935
  • Status: closed  
  • Source: Technical University Berlin ( Markus Helmke)
  • Summary:

    The interface Parameter provides four functions · string get_expression() raises (CadUtility::CadError); · void set_expression(in string e_value) raises (CadUtility::CadError); // operations to allow an expression that may drive geometry

    · CadUtility::EntityAttrib get_value() raises (CadUtility::CadError); · void set_value (in CadUtility::EntityAttrib value) raises (CadUtility::CadError); // operations providing access to parameter value Actually “Parameter” is an easy interface. But since we have seen different implementation approaches and since it was not clear for us in every case too what should be handed over to the set-methods and what could be retrieved by the get-methods I write down our assumptions and hope that it will be corrected if that was not the approach you have had in mind: A parameter covers expressions like “a=6” or “a=b+c”, where “a” is the “name” of the expression. getValue() therefore will return the recursive computed value in the case of “b+c” or an error when there is a problem with the computation. In case of “6” getValue() will just return the value “6”. setValue() allows to set a value if the value of “is_read_only” has the value “false”. The type of the handed over value must match the type of CadUtility::EntityAttrib stored by parameter. In the case of “a=6” “is_independent” keeps the value true. In the case “a=b+c” “is_independent” turns to the value “false”. It is a question whether handing over a value like “8” should be allowed at all when the parameter carries an non numeric expression. getExpression() is similar to getValue() with the difference that the return type is a string. setExpression() allows to set expressions like “d+e” or “8”. The values of “is_independent” and “is_read_only” have to be set accordingly. Expression like “a=d+e” and “a=8” should be possible but internally the expression is parsed and “a=” is ignored. Expression like “b=d+k” should be forbidden because they provide a back door to define completely new parameter when name is set to “b”. If this also has been intended this should be made clear. But I guess this would require extra methods that allow to define parameter. Summing up it is actually no problem to omit the value-methods The “expression”-methods can take over the task to handle values because these also can be represented by expressions like “8”.

  • Reported: CAD 1.0 — Wed, 7 May 2003 04:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Set color on Layer interface

  • Key: CAD11-28
  • Legacy Issue Number: 5776
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    The Layer interface needs a set_color() operation

  • Reported: CAD 1.0 — Tue, 19 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Operation to identify opened Models

  • Key: CAD11-29
  • Legacy Issue Number: 5777
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    The existing interfaces on the CadSystem interface do not indicate CadMain::Model references that may be opened and available for immediate use

  • Reported: CAD 1.0 — Tue, 26 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadFoundation.idl: In the CadFoundation::EntityPropsStruct

  • Key: CAD11-32
  • Legacy Issue Number: 5848
  • Status: closed  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    CadFoundation.idl: In the CadFoundation::EntityPropsStruct the variable global_position is never mentioned in the pdf file. Besides: The corresponding method to global_position in CadFoundation::Entity is named global_location. Shouldn't that be either both position or both location?

  • Reported: CAD 1.0 — Fri, 24 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT

bounding_box" behavior

  • Key: CAD11-31
  • Legacy Issue Number: 5842
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    An empty TypeCodeSeq in Model::bounding_box() and Model::top_level_entities() will be handled differently according to the comments in the IDL-files. In bounding_box it means all entities and in top_level_entities it should generate a BadParam exception. Would it not be better, to give it in both methods a similar meaning?

    Recommend "bounding_box" behavior.

  • Reported: CAD 1.0 — Fri, 17 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add operations to CadMain::Model

  • Key: CAD11-30
  • Legacy Issue Number: 5841
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    void add_child(in Model child_model) raises (CadUtility::CadError);
    void remove_child(in Model child_model) raises (CadUtility::CadError);
    It is suggested that Model be changed to ModelInstance to allow for assemblies

  • Reported: CAD 1.0 — Fri, 17 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

struct PolyLineStruct is defined but not used anywhere

  • Key: CAD11-33
  • Legacy Issue Number: 5849
  • Status: closed  
  • Source: CAxOPEN GmbH ( Bernd Swienczek)
  • Summary:

    struct PolyLineStruct is defined but not used anywhere. Either the according interface PolyLine is missing or the struct is obsolete

  • Reported: CAD 1.0 — Fri, 24 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    PolyLineStruct is obsolete and should be removed.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

"Entity-Types"

  • Key: CAD11-24
  • Legacy Issue Number: 5752
  • Status: closed  
  • Source: Anonymous
  • Summary:

    In some methods (mainly Model-Interface) "Entity-Types" are demanded as an
    selection mechanism to select appropriate entities. Example:

    CadFoundation::EntitySeq top_level_entities (
    in CadUtility::TypeCodeSeq entity_types)

    But the CAD-Services provide no opportunity to implement a method that
    allows to ask for these entity types that are supported by the respective
    CAD-System. But in our mind it is up to the CAD-System and thus to the
    CAD-Services to provide such information

  • Reported: CAD 1.0 — Fri, 8 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above, issue rejected

  • Updated: Fri, 6 Mar 2015 20:58 GMT

"Cadsystem" interface issue

  • Key: CAD11-25
  • Legacy Issue Number: 5753
  • Status: closed  
  • Source: Anonymous
  • Summary:

    The interface "Cadsystem" provides access on a "CadUserInterface" by the
    method

    boolean is_interactive(out CadUserInterface gui);

    Normally loading a model in the CAD engine and showing it with the editor
    are two different tasks.
    "create_model" and "open_model" obvioulsy are related to CAD-Engine
    activity. GUI activities like showing, hiding etc. are not mandatory
    implicated. If methods like "create_model" and "open_model" are intended not
    to include GUI operation then functionality to control the
    "CadUserInterface" is missing.
    Therefore the following function would be very helpful (They assume that a
    model is already loaded by the CAD engine):

    createWindow(model) // Creates a window and put it in the foreground
    hideWindow(model) // hides an existing window but doesn't
    delete it
    foregroundWindow(model) // put an existing (even if hided) window in the
    foreground
    deleteWindow(model) // delete the window and the corresponding window
    data structure but NOT the model within the CAD engine

    Every model should throw a "ModelNotLoadedException" if the model is not
    loaded.

    Summing up this should allow for a separated control of activities within
    the CAD-engine and the editor.

  • Reported: CAD 1.0 — Fri, 8 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

interface Model : CadFoundation:: Attributable replaced

  • Key: CAD11-26
  • Legacy Issue Number: 5774
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    interface Model : CadFoundation:: Attributable

    was replaced by

    interface Model : CadFoundation:: Entity

    This is an issue I've posted many times ago. This really simplify the
    life with implementation and classification of entities.

  • Reported: CAD 1.0 — Tue, 19 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    The inheritance for Model is changed as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

remove CadGeometryExtens interface

  • Key: CAD11-27
  • Legacy Issue Number: 5775
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    I propose to remove CadGeometryExtens interface:
    module CadGeometryExtens{

    interface Point : CadFoundation :: Entity

    { CadUtility::PointStruct coords() raises (CadUtility::CadError); }

    ;

    struct PointOnSurfaceStruct

    { CadGeometry::Surface basis_surface; CadUtility::UvStruct the_point; }

    ;

    interface PointOnSurface : Point

    { PointOnSurfaceStruct pos_info() raises (CadUtility::CadError); }

    ;

    struct PointOnCurveStruct

    { CadGeometry::Curve basis; double crv_param; }

    ;

    interface PointOnCurve : Point

    { PointOnCurveStruct poc_info() raises (CadUtility::CadError); }

    ;

    It seems to be quite unuseful

  • Reported: CAD 1.0 — Tue, 19 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Tessellation Types

  • Key: CAD11-22
  • Legacy Issue Number: 5750
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    For example, consider the requirements for calling Body::tessellate():
    ConnectedFaceTessellationStruct
    tessellate(in TessType t_type,
    inout TessParametersStruct params,
    out boolean flag);

    The first argument (the tessellation type) can be one of two enumerated values, WIREFRAME or VISUALIZATION. Nowhere in the specification is any hint given as to the difference between these two settings. One might guess that the VISUALIZATION tessellation type produces a larger number of triangles, but to what degree? Is it implementation-dependent?

  • Reported: CAD 1.0 — Wed, 6 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Curve Parameters

  • Key: CAD11-23
  • Legacy Issue Number: 5751
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    The Edge::start_parameter() and Edge::end_parameter() operations return the "curve parameter corresponding to the start (end) vertex". I suppose this is referring to the parametric distance along the underlying curve, but it's unclear because of the sort-of generic use of the word "parameter".

  • Reported: CAD 1.0 — Wed, 6 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Euclidean Dimension

  • Key: CAD11-21
  • Legacy Issue Number: 5749
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    The Entity::euclidean_dimension() operation is described as returning the "Euclidean dimension of the entity" (with type long). What is this referring to? My guess is that it returns 2 for two-dimensional entities or 3 for three-dimensional entities, but this is unclear

  • Reported: CAD 1.0 — Wed, 6 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    Additional documentation is needed

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Documentation for CadMain::Model::unique_entities()

  • Key: CAD11-17
  • Legacy Issue Number: 5912
  • Status: open  
  • Source: CAxOPEN ( Andreas Korn)
  • Summary:

    2. The Documentation for CadMain::Model::unique_entities() and CadMain::Model::top_level_entities() says the only valid types asked for are geometric entity types but there is only mention and used CadFoundation::Entity (in the doc and in the return types). If this should really be only geometric entities, the return types could be CadBrep::BrepEntity and the documentation should be much clearer on what is allowd and what a invalid type.

  • Reported: CAD 1.1 — Wed, 23 Apr 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Model Instances vs. Top-Level Entities

  • Key: CAD11-19
  • Legacy Issue Number: 5747
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    The distinction between model instances and top-level entities was unclear to me, especially so given my task of trying to write a general purpose tool to "import" arbitrary CAD models into CFD-GEOM via the CAD Services interface. A Model can contain zero or more ModelInstances, and this provides support for assemblies. At the same time, certain entities in a Model are designated as top-level entities, which also brings to mind the concept of a composition or assembly.

  • Reported: CAD 1.0 — Wed, 6 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    Additional text is needed in the documentation

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add some operations to CadFoundation module's interfaces

  • Key: CAD11-18
  • Legacy Issue Number: 5729
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    It's necessary to add some operations to CadFoundation module's interfaces:

    CadFoundation::Entity::SetColor(CadUtility::ColorStruct color) raises (CadUtility::CadError);
    CadFoundation::Layer::SetColor(CadUtility::ColorStruct color) raises (CadUtility::CadError);

  • Reported: CAD 1.0 — Tue, 29 Oct 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    The recommended changes are made as suggested in the summary

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityFactory and ModelInstanceFactory

  • Key: CAD11-20
  • Legacy Issue Number: 5748
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    I was already familiar with the Factory design pattern and so the purpose of the EntityFactory and ModelInstanceFactory interfaces was immediately obvious to me. I'm not sure how familiar other users of the CAD Services will be with this pattern, depending on their software development background.

  • Reported: CAD 1.0 — Wed, 6 Nov 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.1
  • Disposition Summary:

    The documentation shall clarify the intent of these "Factory" interfaces

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Data in CadGeometry::EdgeTessellationStuct

  • Key: CAD11-15
  • Legacy Issue Number: 5882
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    I have a problem understanding how to interpret the
    > vertex_number's for
    > the points in CadGeometry::EdgeTessellationStuct. I don't see
    > the need
    > for a indexing here. It is just sequencial. Are there people,
    > who want
    > to do this another way?

  • Reported: CAD 1.1 — Fri, 14 Mar 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadMain::Model interface issue

  • Key: CAD11-16
  • Legacy Issue Number: 5911
  • Status: open  
  • Source: CAxOPEN ( Andreas Korn)
  • Summary:

    CADServices 1.1
    1. In The CadMain::Model interface there is no clear way to get the DesignFeatures of a Model. The only possible way would be via top_level_entities() or unique_entities(), but these calls are for geometric entities (so it is written in the documentation).
    Proposed Solution: add a call "CadFeature::DesignFeatureSeq design_features()" to CadMain::Model. The DesignFeatures should be more clearly seperated from the BrepEntities as they are to different sights on the same data and should not be mixed per chance.

  • Reported: CAD 1.1 — Wed, 23 Apr 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

CADServices 1.1 issue

  • Key: CAD11-14
  • Legacy Issue Number: 5881
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    In the PDF document (03-02-02) for the CadServices the return value for CadFoundation::Entity::reference_position is CadUtility::PointStruct, but in the idl files it is CadUtility::PointStructSeq.
    I couldn't verify it against the newest documents (maybe newer than mine), because they were unreachable.
    Besides, the description of this method is not very helpful (at least to me). I have no clue how to interpret it.

  • Reported: CAD 1.1 — Thu, 13 Mar 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadBrep::OrientedEdge interface issue

  • Key: CAD11-13
  • Legacy Issue Number: 5878
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    The CadBrep::OrientedEdge interface has two very similar methods to get the Face/OrientedFace which uses the OrientedEdge. That's pretty redundant. Besides: Both methods deliver useful information only when the OrientedEdge belongs to one and only one Face. Otherwise an exception is generated. I don't really see the usefulness of those two method, especially since for many cases there are two Faces for the Edge and one can always traverse there via the EdgeLoop.

  • Reported: CAD 1.1 — Mon, 3 Mar 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadBrep module issue

  • Key: CAD11-12
  • Legacy Issue Number: 5877
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    In the CadBrep module there are almost always two ways to traverse the topology: from the top level entities like Body to the underlying entites like Shell, Face, Edge, ... and the other way. For example I can get from Face to the OrientedFace which aggregates the Face or I can ask the OrientedShell in which Body it is contained. This does not make much sense to me. I always thought the topology is more or less hierarchical with Body is composed of OrientedShells which has reference to Shell and so on.
    Unless I am missing something important, it is just some not so small overhead to have all those relations at hand and being uptodate with them. I would place such things in a client for I see it as application specific, if it is neccessary or not.

  • Reported: CAD 1.1 — Mon, 3 Mar 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

method CadMain::Model::unique_ids_to_entities()

  • Key: CAD11-11
  • Legacy Issue Number: 5873
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    The method CadMain::Model::unique_ids_to_entities() can throw the CadMain::NotValidCadType exception but unlike the other methods able to throw this does not get TypeCodes as input. If the exception is there by accident I suggest it be removed.

  • Reported: CAD 1.1 — Thu, 27 Feb 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

description for CadMain::Model::unique_ids_to_entities() is missing

  • Key: CAD11-10
  • Legacy Issue Number: 5872
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    In the PDF document for CADServices 1.1 (03-02-02) the description for CadMain::Model::unique_ids_to_entities() is missing

  • Reported: CAD 1.1 — Thu, 27 Feb 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

return value of CadFoundation::Entity::cad_model()

  • Key: CAD11-8
  • Legacy Issue Number: 5851
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    The return value of CadFoundation::Entity::cad_model() is Object. It would be clearer if it would return CadMain::Model (forward declaration).

  • Reported: CAD 1.0 — Wed, 29 Jan 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadFoundation::EntityPropsStruct

  • Key: CAD11-6
  • Legacy Issue Number: 5847
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    In CadFoundation::EntityPropsStruct one variable is named ref_position in the pdf and ref_positions in the idl files. Should be ref_position

  • Reported: CAD 1.0 — Fri, 24 Jan 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

exception CadConnection::BadParameter does not match the method anymore

  • Key: CAD11-9
  • Legacy Issue Number: 5855
  • Status: open  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    after changing the fourth parameter of CadConnection::CadSystem::create_model from CadFeature::ParameterSeq to CosPropertySevice::Properties recently, the exception CadConnection::BadParameter does not match the method anymore.
    It should either be changed in a similar manner or kicked out completely (it is only used by create_model).

  • Reported: CAD 1.1 — Tue, 11 Feb 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

different tessellation structures for different kind of entities

  • Key: CAD11-7
  • Legacy Issue Number: 5850
  • Status: open  
  • Source: Anonymous
  • Summary:

    There are some different tessellation structures for different kind of entities (geometric and topologic) and some are for both (e.g. EdgeTessellationStruct). Three of the four structs have a obj_ref member with type Object.

    Issues: 1. The type Object for obj_ref is too generic. 2. Some of the tessellation structs are for the use with one single interface (ConnectedFaceTessellationStruct -> Body) while some others are used in more than one interface (EdgeTessellationStruct -> Edge, Curve). 3. In some cases the obj_ref member of a single tessellation struct references a geometric entity (Curve, Surface), in others a topologic entity (Edge, Face, Body)

    Proposed Solution: For each interface which provides tessellation (has a tessellate() method) there should be one corresponding tessellation struct with a obj_ref member of the type of the interface which generated the struct.

    Edge -> EdgeTessellationStruct Face -> FaceTessellationStruct Curve -> CurveTessellationStruct Surface -> SurfaceTessellationStruct Body -> ConnectedFaceTessellationStruct

    It would be much clearer that way and the redundancies pretty few.

  • Reported: CAD 1.1 — Wed, 29 Jan 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Model creation parameters

  • Key: CAD11-5
  • Legacy Issue Number: 5843
  • Status: open  
  • Source: NASA ( Russ Claus)
  • Summary:

    Where can one get the CadFeature::Parameter instances from to use in CadSystem::create_model() ?
    As far as I know, the instance of a idl interface can only be created on the server (in a get method or in a factory) and I can see no way of creating empty CadFeature::Parameter instances.
    Besides, why was CadFeature::ParameterSeq used on Model level (CadMain::Model::create_model(), CadMain::Model::get_parameter_set()) and not as in other places CosProperyService::Properties? It is not clear to me, what information is supposed to be behind these parameters.

    This looks like a valid concern. We can fix this by using either CosProperyService::Properties in place of the CadFeature::ParameterSeq or we can created a CadFeature::ParameterFactory.

    I suggest the use of Properties.

  • Reported: CAD 1.1 — Tue, 21 Jan 2003 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

struct HyperbolaStruct should be moved from CadSurface to CadCurve

  • Key: CAD11-2
  • Legacy Issue Number: 5097
  • Status: open  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    struct HyperbolaStruct

    { CadUtility::TransformationStruct location; double semi_axis; double semi_imag_axis; }

    ;
    Should be moved from module CadSurface to CadCurve, because it is used
    only by "curve"
    interfaces.

  • Reported: CAD 1.0 — Fri, 29 Mar 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

File CadMain: Method add_child and remove_child

  • Key: CAD11-4
  • Legacy Issue Number: 5099
  • Status: open  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    File CadMain:

    1. Method add_child and remove_child from CadMain::Model should has
    CadMain::ModelInstance in parameter instead of CadMain::Model.

  • Reported: CAD 1.0 — Fri, 29 Mar 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

File CadGeometryExtens

  • Key: CAD11-1
  • Legacy Issue Number: 5096
  • Status: open  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    File CadGeometryExtens:

    1.
    struct SurfacePatchStruct

    { BoundedSurface parent_surface; TransitionCode u_transition; TransitionCode v_transition; boolean u_sense; boolean v_sense; }

    ;
    Should be
    struct SurfacePatchStruct

    { CadGeomerty::Surface parent_surface; TransitionCode u_transition; TransitionCode v_transition; boolean u_sense; boolean v_sense; }

    ;
    because parent_surface can be any type.

  • Reported: CAD 1.0 — Fri, 29 Mar 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

struct OffsetCurveStruct

  • Key: CAD11-3
  • Legacy Issue Number: 5098
  • Status: open  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    struct OffsetCurveStruct

    { double distance; CadUtility::VectorStruct ref_direction; boolean self_intersect; }

    ;
    Should contain also field CadGeometry::Curve BasisCurve.

  • Reported: CAD 1.0 — Fri, 29 Mar 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT