Computer Aided Design Services Avatar
  1. OMG Specification

Computer Aided Design Services — Closed Issues

  • Acronym: CAD
  • Issues Count: 65
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
CAD12-5 CadConnection, CadSystem: Avaliable_models() enhancement CAD 1.1 CAD 1.2 Resolved closed
CAD12-2 Suggest altering the input parameter CadFeature::ParameterSeq model_params CAD 1.1 CAD 1.2 Resolved closed
CAD12-1 altering the use of EntitySeqs to LongSeqs CAD 1.1 CAD 1.2 Resolved closed
CAD12-4 CadMain::ModelInstance::component()' collides CAD 1.1 CAD 1.2 Resolved closed
CAD12-3 CadGeometry::Curve::tessellate() CAD 1.1 CAD 1.2 Resolved closed
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-21 Euclidean Dimension CAD 1.0 CAD 1.1 Resolved closed
CAD11-20 EntityFactory and ModelInstanceFactory CAD 1.0 CAD 1.1 Resolved closed
CAD11-34 interface Parameter CAD 1.0 CAD 1.1 Resolved closed
CAD11-25 "Cadsystem" interface issue CAD 1.0 CAD 1.1 Resolved closed
CAD11-24 "Entity-Types" CAD 1.0 CAD 1.1 Resolved closed
CAD11-23 Curve Parameters CAD 1.0 CAD 1.1 Resolved closed
CAD11-22 Tessellation Types CAD 1.0 CAD 1.1 Resolved closed
CAD11-27 remove CadGeometryExtens interface CAD 1.0 CAD 1.1 Resolved closed
CAD11-26 interface Model : CadFoundation:: Attributable replaced 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-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-29 Operation to identify opened Models CAD 1.0 CAD 1.1 Resolved closed
CAD11-28 Set color on Layer interface CAD 1.0 CAD 1.1 Resolved closed
CAD-15 What are units for 'angle' field in TessParametersStruct CAD 1.0b1 CAD 1.0 Resolved closed
CAD-14 TessellationStruct normals field should be VectorStructSeq CAD 1.0b1 CAD 1.0 Resolved closed
CAD-13 Should there be a get_parameter_set function at the Model interface level? CAD 1.0b1 CAD 1.0 Resolved closed
CAD-12 CadBrep Edge.nearest_points function needs clarification CAD 1.0b1 CAD 1.0 Resolved closed
CAD-11 CadBrep Edge.nearest_points function incorrect CAD 1.0b1 CAD 1.0 Resolved closed
CAD-10 CAD Services IDL issue (02) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-9 CAD Services IDL issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-8 Binding for Face.nurbs_representation needs major design overhaul/removal CAD 1.0b1 CAD 1.0 Resolved closed
CAD-7 CAD Services needs to clarify 'exact' for nurbs_representation functions CAD 1.0b1 CAD 1.0 Resolved closed
CAD-6 Edge.nurbs_representation should h. 'tolerance' argument declared as inout CAD 1.0b1 CAD 1.0 Resolved closed
CAD-5 Surface.nurbs_approximation should 'tolerance' argument declared as inout CAD 1.0b1 CAD 1.0 Resolved closed
CAD-4 Surface.nurbs_approximation should be renamed nurbs_representation CAD 1.0b1 CAD 1.0 Resolved closed
CAD-3 Need to add a "ColorStruct color;" to the PresentationStruct CAD 1.0b1 CAD 1.0 Resolved closed
CAD-2 IDL extracts in document are inconsistent about showing module declarations CAD 1.0b1 CAD 1.0 Resolved closed
CAD-1 CAD FTF issue regarding UML which looks kind of like CORBA profile CAD 1.0b1 CAD 1.0 Resolved closed
CAD-43 Incompletely specified operations - issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-42 Several properties in the CadBrep::PropertyStruct need clarification. CAD 1.0b1 CAD 1.0 Resolved closed
CAD-41 problems in the EntityCreation interface. CAD 1.0b1 CAD 1.0 Resolved closed
CAD-40 Entity Factory issue (Function 5) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-39 Entity Factory issue (Function 4) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-38 Entity Factory issue (Function 3) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-37 Entity Factory issue (Function 2) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-36 Entity Factory issue (Function) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-35 interface for STEP open shel CAD 1.0b1 CAD 1.0 Resolved closed
CAD-34 Deletion of CadFourndation::Entity descendants CAD 1.0b1 CAD 1.0 Resolved closed
CAD-33 Entity.Position() returns PointStructure instead of TransformationStructure CAD 1.0b1 CAD 1.0 Resolved closed
CAD-32 There is no way to delete any CadFoundation::Entity interface child. CAD 1.0b1 CAD 1.0 Resolved closed
CAD-31 CadFoundation::Entity interface CAD 1.0b1 CAD 1.0 Resolved closed
CAD-30 Surface.intersect_ray argument error CAD 1.0b1 CAD 1.0 Resolved closed
CAD-29 CadSystem Properties issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-28 I haven't found any way to create ModelInstance CAD 1.0b1 CAD 1.0 Resolved closed
CAD-27 Replace #include "CadFeature.idl with #include "CadFoundation.idl" CAD 1.0b1 CAD 1.0 Resolved closed
CAD-26 Method names in topological entities are not everywhere unified CAD 1.0b1 CAD 1.0 Resolved closed
CAD-25 how to add new topological entities to existing model with sharing of exist CAD 1.0b1 CAD 1.0 Resolved closed
CAD-24 method of CadMain::EdgeLoop has to be renamed CAD 1.0b1 CAD 1.0 Resolved closed
CAD-23 we have to generalize is_manifold() methods in all BRep entities CAD 1.0b1 CAD 1.0 Resolved closed
CAD-22 adding an attribute to the entity group CAD 1.0b1 CAD 1.0 Resolved closed
CAD-21 Section 3.4, Editorial CAD 1.0b1 CAD 1.0 Resolved closed
CAD-20 Sections 1.8, 2.8, 3.1, 3.2, Editorial CAD 1.0b1 CAD 1.0 Resolved closed
CAD-19 Support for STEP input / output? CAD 1.0b1 CAD 1.0 Resolved closed
CAD-18 Body.property_info, several values are calculated. What is the return accur CAD 1.0b1 CAD 1.0 Resolved closed
CAD-17 BodyTessellationStruct issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-16 Model level parameters for geometry creation issue CAD 1.0b1 CAD 1.0 Resolved closed

Issues Descriptions

CadConnection, CadSystem: Avaliable_models() enhancement

  • Key: CAD12-5
  • Legacy Issue Number: 7140
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Disposition: ?
    OMG Issue No: ?
    Title: CadConnection, CadSystem: Avaliable_models() enhancement
    Source:
    Markus Helmke, Produktionstechnisches Zentrum (PTZ)
    Technische Universität Berlin
    Email: markus.helmke@ipk.fhg.de

    Summary:

    The method "available_models()" provides access to models available to the active CAD System and returns all available models in a list. Up to now the method does not take into account how the models are structured on the server side. When a user selects a model it would be helpful to navigate through the tree structure of the servers file system. A similar problem is the specification of a users file name in that moment when he wants to use "save_model_as()" or "create_model()".
    The proposed methods, data structures and definitions aim to improve navigation capabilities for both systems and users when accessing models. For various reasons a native CAD-system normally is able to access different directories which are presented also to the user. This is to let him structure his work but also in order to offer templates that ease the design process, because in most cases designer aren't starting from scratch, but they are provided with templates that cover predefined parameters or a special design philosophy.
    Assuming a user wants to store, create, or open a model on the (maybe remote) machine running the Cad-Services he expects something like a "FileChooser"-dialog. The method "available_models()" was not designed to support such functionality and therefore needs to be extended.
    The proposed methods allow for implementing the intended functionality because they represent an essential subset of methods needed to do the following:

    • Navigation (get_root_directories(), get_models_and_folders(), get_parent_directory())
    • Create new subfolder (create_new_folder())
    • Providing information to choose a file or folder on the client side (get_models_and_folders())
      The concept provides the possibility not to expose the whole file system to the user by using "root_directories". Every directory can serve as root directory and thus only its subdirectories are exposed to the user. The user starts navigation in the one of the roots.
      The methods were taken from JAVA's abstract class "javax.swing.filechooser.FileSystemView" which serves as "JFileChooser's gateway to the file system" and as such promise to be sufficient. Additionally IWF has implemented against the proposed CAD-Services enhancement with success.

    Resolution:
    ?

    Revised Text:
    The following typedefs, struct and operations are added to the CadConnection module respectively to the CadSystem interface:

    module CadConnection
    {

    struct Path

    { boolean is_dir; // Indicates whether Path represents a file or a directory string path; // Canonical, absolute, and unique path representing a file or // a directory }

    ;

    typedef sequence<string> RootsList;
    typedef sequence<Path> PathList;

    interface CadSystem

    { // Creates a new folder in a given directory. // param parent_dir: The (canonical, absolute, and unique) path of the // directory, in which the folder will be created. This must be either // one of the root directories (see get_root_directories()) or a // directory that exists in one of the root directory's subdirectories // param folder_name: The name of the folder to be created. It must be a // valid and a not already existing name. // raises CadUtility::CadError: If there was an error in creating the // folder. void create_new_folder(in string parent_dir, in string folder_name) raises (CadUtility::CadError); // Returns a list of (canonical, absolute, and unique) pathnames repre- // senting the root directories. In a root directory or in any other // subdirectory, model files can be found. // return: List of pathnames representing root directories. RootsList get_root_directories(); // Returns a list of subdirectories and model files of a given directory. // param directory: (canonical, absolute, and unique) path of the // directory from which to get the list of subdirectories and model // files. This must be either one of the root directories or a subdirectory. // return: A list representing subdirectories and/or model files // of the given directory. // raises CadUtility::CadError If there was an error retrieving the list. PathList get_models_and_folders(in string directory) raises (CadUtility::CadError); // Returns the parent directory of a given directory. // param directory: (canonical, absolute, and unique) path of the // directory from which to get its parent directory. The given directory // should be a subdirectory of one of the root directories. // return: The path of the parent directory. // raises CadUtility::CadError If there was an error retrieving the // parent directory. string get_parent_directory(in string directory) raises (CadUtility::CadError); }

    ;
    };

    Disposition: ?
    Disposition Parameter: ?

  • Reported: CAD 1.1 — Wed, 10 Mar 2004 05:00 GMT
  • Disposition: Resolved — CAD 1.2
  • Disposition Summary:

    see below

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

Suggest altering the input parameter CadFeature::ParameterSeq model_params

  • Key: CAD12-2
  • Legacy Issue Number: 5845
  • Status: closed  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    Suggest altering the input parameter CadFeature::ParameterSeq model_params on CadConnection::CadSystem to a CosPropertyService::Properties

  • Reported: CAD 1.1 — Wed, 22 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.2
  • Disposition Summary:

    This issue was previously (v 1.1) resolved

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

altering the use of EntitySeqs to LongSeqs

  • Key: CAD12-1
  • Legacy Issue Number: 5844
  • Status: closed  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    I suggest altering the use of EntitySeqs to LongSeqs - essentially to use Unique IDs as identifiers. [In places like: Model::delete_entity(), EntityGroup::add_entities(), EntityGroup::remove_entities()] I see there 2 main problems: 1. I don't see that it is really neccesssary to use the (in this case Entity objects) CORBA objects to identify an object. unique_id's could always be used. -> Less traffic and a lot easier to map. Besides: how much sense does the UidUnsupported exception make? unique ids can always be created. 2. The required mapping especially on the server side is somewhat tricky and not the fastest. You would have to map the CORBA objects to the implementation objects. Nasty thing to do.

  • Reported: CAD 1.1 — Wed, 22 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.2
  • Disposition Summary:

    see below

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

CadMain::ModelInstance::component()' collides

  • Key: CAD12-4
  • Legacy Issue Number: 6693
  • Status: closed  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    'CadMain::ModelInstance::component()' collides with the new 'component' keyword for IDL from CCM.

    I suggest ro rename it to 'CadMain::ModelInstance::component_model()'.

  • Reported: CAD 1.1 — Thu, 11 Dec 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.2
  • Disposition Summary:

    see below

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

CadGeometry::Curve::tessellate()

  • Key: CAD12-3
  • Legacy Issue Number: 5846
  • Status: closed  
  • Source: CAxOPEN GmbH ( Andreas Korn)
  • Summary:

    is there any reason, why the double parameter (tolerance) of CadGeometry::Curve::tessellate() is declared as an in parameter and not inout? In other places like CadGeometry::Surface::nurbs_representation() the tolerance parameter is declared inout.

  • Reported: CAD 1.1 — Wed, 22 Jan 2003 05:00 GMT
  • Disposition: Resolved — CAD 1.2
  • Disposition Summary:

    see below

  • 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

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

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

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

"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

"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

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

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

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

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

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

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

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

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

What are units for 'angle' field in TessParametersStruct

  • Key: CAD-15
  • Legacy Issue Number: 4538
  • Status: closed  
  • Source: Westinghouse Electric ( Jim Jones)
  • Summary:

    adGeometry IDL comment documents the 'angle' field in CadGeometry.TessParametersStruct
    as "deviation between normals of facets".

    Neither the IDL nor the CAD Services spec. indicate what angular units should be used.

  • Reported: CAD 1.0b1 — Mon, 27 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This oversight was corrected by indicating the required use of degrees for angle units.

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

TessellationStruct normals field should be VectorStructSeq

  • Key: CAD-14
  • Legacy Issue Number: 4537
  • Status: closed  
  • Source: Westinghouse Electric ( Jim Jones)
  • Summary:

    The type of the 'normals' field in TessellationStruct should be VectorStructSeq
    instead of PointStructSeq.

  • Reported: CAD 1.0b1 — Mon, 27 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. IDL modified.

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

Should there be a get_parameter_set function at the Model interface level?

  • Key: CAD-13
  • Legacy Issue Number: 4528
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Should there be a get_parameter_set function at the Model interface level?

  • Reported: CAD 1.0b1 — Mon, 20 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

CadBrep Edge.nearest_points function needs clarification

  • Key: CAD-12
  • Legacy Issue Number: 4493
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Edge.nearest_points function needs clarification for
    'nearest_points' argument.

    How are the nearest_points defined? It is declared as a PointStructSeq,
    but no further details are provided. Will there always be 2? Is the
    first point of the sequence a point on the given edge and the second
    point a point on the edge corresponding to the input argument? What is
    the expected behavior if there are multiple locations that the 2 edges
    have an identical minimum distance?

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

CadBrep Edge.nearest_points function incorrect

  • Key: CAD-11
  • Legacy Issue Number: 4492
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Edge.nearest_points function incorrectly defines the
    'nearest_points' argument as 'in'.

    CAD Services spec documents Edge.nearest as 'Determines the minimum
    distance, and corresponding closest points, between this Edge and the input
    Edge. The returned value is the minimum distance'. The 'nearest_points'
    argument should be declared as 'out'.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Resolved through removing the nearest_points operation. See issue 4493.

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

CAD Services IDL issue (02)

  • Key: CAD-10
  • Legacy Issue Number: 4491
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Edge IDL defines a 'start_vertex()' function, but not
    an 'end_vertex()' function.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. An operation was added to the Edge interface.

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

CAD Services IDL issue

  • Key: CAD-9
  • Legacy Issue Number: 4490
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Oriented Edge IDL defines an 'end_vertex()' function,
    but not a 'start_vertex()' function.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. An operation was added to the OrientedEdge interface

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

Binding for Face.nurbs_representation needs major design overhaul/removal

  • Key: CAD-8
  • Legacy Issue Number: 4489
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Binding for Face.nurbs_representation needs major design overhaul or
    removal.

    IDL indicates the function returns a CadUtility.NurbsSurfaceStruct. A
    simple NURBS surface structure cannot represent arbitrary faces w/
    irregular boundaries, both outer and inner.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

CAD Services needs to clarify 'exact' for nurbs_representation functions

  • Key: CAD-7
  • Legacy Issue Number: 4488
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CAD Services specification needs to clarify 'exact' for
    nurbs_representation functions.

    nurbs_representation indicates that if the NURBS is exact, then tolerance
    is returned as negative value. Is that exact geometrically or exact
    geometrically AND parametrically?

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Edge.nurbs_representation should h. 'tolerance' argument declared as inout

  • Key: CAD-6
  • Legacy Issue Number: 4487
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Edge.nurbs_representation should h. 'tolerance' argument declared as
    'inout' instead of 'in'.

    CAD Services specification indicates that 'If the representation is exact -
    tolerance will be returned as a negative value.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. This corrections involved a minor modification of the IDL.

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

Surface.nurbs_approximation should 'tolerance' argument declared as inout

  • Key: CAD-5
  • Legacy Issue Number: 4486
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Surface.nurbs_approximation should have 'tolerance' argument declared as
    'inout' instead of 'in'.

    CAD Services specification indicates that 'If nurbs representation is
    exact, tolerance will be returned as a negative'. By the way, the 'NURBS'
    acronym should be capitalized in the spec and IDL when used in this
    context.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Surface.nurbs_approximation should be renamed nurbs_representation

  • Key: CAD-4
  • Legacy Issue Number: 4485
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Surface.nurbs_approximation should be renamed nurbs_representation to be
    consistent w/ Curve.nurbs_representation.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agree. Representation is a better description

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

Need to add a "ColorStruct color;" to the PresentationStruct

  • Key: CAD-3
  • Legacy Issue Number: 4433
  • Status: closed  
  • Source: Anonymous
  • Summary:

    I was building a Java3d display for CadServices data and I realized that
    > we do not return the object color in the PresentationStruct. We return
    > the color of the highlight (specular_color), and various parameter about
    > reflectance - but we do not include the base color of the object.
    >
    > I think we need to add a "ColorStruct color;" to the PresentationStruct.

  • Reported: CAD 1.0b1 — Fri, 27 Jul 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

IDL extracts in document are inconsistent about showing module declarations

  • Key: CAD-2
  • Legacy Issue Number: 4415
  • Status: closed  
  • Source: Distributed Models Pty Ltd ( Keith Duddy)
  • Summary:
    • IDL extracts in the document are inconsistent about showing module
      declarations.
  • Reported: CAD 1.0b1 — Sat, 14 Jul 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Module declarations added to the document

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

CAD FTF issue regarding UML which looks kind of like CORBA profile

  • Key: CAD-1
  • Legacy Issue Number: 4414
  • Status: closed  
  • Source: Distributed Models Pty Ltd ( Keith Duddy)
  • Summary:

    UML looks like Corba profile, but is not quite. In particular the
    <<Interface>> stereotype should be <<CORBAInterface>>. There may also
    be some "in" tags in the wrong place.

  • Reported: CAD 1.0b1 — Sat, 14 Jul 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    CORBA UML diagrams throughout the document were updated to an appropriate format

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

Incompletely specified operations - issue

  • Key: CAD-43
  • Legacy Issue Number: 4985
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Mikhail Kazakov mentioned that some of the Cad Services interfaces may be under-specified. Here is a list of operations needing additional documentation:
    1. CadMain:: open_model( Â…) - the question involves whether this operation loads the specified model into memory or are all the available models in memory and the open_model() operation merely returns an object reference to the model.

    Recommendation: the documentation should include the following: The open_model() operation loads the specified model into memory and can be unloaded by invoking close_model() on the Model object reference.

    2. CadMain:: top_level_entities (in CadUtility::TypeCodeSeq entity_types) - what happens when an empty TypeCodeSeq is passed? One could respond with all top level entities or none.
    Recommendation: Documentation shall state that an empty TypeCodesSeq will result in a system exception (BAD_PARAM).

    3. unsigned long unique_entities_count (in CadUtility::TypeCodeSeq entity_types) raises (NotValidCadType, CadUtility::CadError); - what happens when an empty TypeCodeSeq is passed? One could respond with all entites or none.
    Recommendation: Documentation shall state that an empty TypeCodesSeq will result in a system exception (BAD_PARAM).

    4. CadFoundation::EntitySeq unique_entities (in CadUtility::TypeCodeSeq entity_types) raises (NotValidCadType, CadUtility::CadError); – what happens when an empty TypeCodeSeq is passed? One could respond with all entites or none.
    Recommendation: Documentation shall state that an empty TypeCodesSeq will result in a system exception (BAD_PARAM).

  • Reported: CAD 1.0b1 — Mon, 18 Mar 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    The identified recommendations were agreed.

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

Several properties in the CadBrep::PropertyStruct need clarification.

  • Key: CAD-42
  • Legacy Issue Number: 4653
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    double inertial_moment_spherical;
    double gyration_radius_spherical;
    CadUtility::VectorStruct first_moments_centroidal;
    CadUtility::VectorStruct inertial_moments_centroidal;
    CadUtility::VectorStruct inertial_products_centroidal;
    CadUtility::VectorStruct principle_moments_centroidal;
    CadUtility::VectorStruct gyration_radii_centroidal;

    are unclear.

    Jim Stevens identified the following:

    The "centroidal" moments are the various mass properties with respect to the center of mass for the body. This is the more "typical" case for mass properties. They correspond to similar mass property calculations in the structure that are with respect to a specific coordinate system.
    Principle moments are moments inertia along the principle axes through the center of gravity of an object.
    When defining a moment of inertia around an arbitrary axis thru the center of mass you end up with product terms. There is
    one axis definition for which the product terms are zero, which is called the principle axis and the moments of inertia when
    using that axis definition are the principle moments.
    Radius of gyration is related to the moments of inertia and the mass along each axis.
    I am not sure about the meaning of first moments. I am pretty sure that inertial_moment_spherical and
    gyration_radius_spherical have to do with representing the model with a single sphere that would have
    the same overall inertial characteristics as the analyzed body.
    Jim Stephens

    Based on Jim's comments I am not certain that we need the first moments or the spherical inertial moment and gyration radius.

  • Reported: CAD 1.0b1 — Wed, 31 Oct 2001 05:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

problems in the EntityCreation interface.

  • Key: CAD-41
  • Legacy Issue Number: 4632
  • Status: closed  
  • Source: TranscenData ( Jim Jones)
  • Summary:

    Here is a quick itemization of necessary changes (most from Sergey and
    a few additional). Following the list is a modified section of the IDL
    that can be used to replace the corresponding lines in the existing
    CadMain.idl file. *** NOTE: Also need to add 'typedef sequence<LongSeq> LongSeqSeq;'
    to CadUtility.idl.

    index_faces:
    Needs 'SeqSeq' of oriented_eloops instead of 'Seq'
    For consistency, arg should probably be 'oriented_edge_loops' instead of 'oriented_eloops'
    Does not need eloops, edges.
    index_edge_loops:
    Needs 'SeqSeq' oriented_edges instead of 'Seq'
    index_shells:
    Needs 'SeqSeq' oriented_faces instead of 'Seq'
    index_bodies:
    Needs 'SeqSeq' oriented_shells instead of 'Seq'
    index_vertex_loops:
    Ok (just included in IDL below for easier replacement of old IDL section)
    index_oriented_edges
    Need 'BooleanSeq senses'
    index_oriented_faces
    Need 'BooleanSeq senses'
    No vertices or vLoops needed
    index_oriented_edge_loops
    For consistency, should probably be 'index_oriented_edge_loops' not 'index_oriented_edgeloops'
    Need 'Seq edge_loops' not 'Seq edges'
    Need 'BooleanSeq senses'
    index_oriented_shells:
    Need 'Seq shells' not 'Seq ofaces'
    Need 'BooleanSeq senses'
    No vloops needed

    CadUtility::LongSeq index_faces(in CadUtility::LongSeqSeq oriented_edge_loops,
    in CadUtility::LongSeq vertex_loops, in CadUtility::LongSeq surfaces)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_edge_loops(in CadUtility::LongSeqSeq oriented_edges)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_shells (in CadUtility::LongSeqSeq oriented_faces)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_bodies (in CadUtility::LongSeqSeq oriented_shells)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_vertex_loops (in CadUtility::LongSeq vertices)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_edges(in CadUtility::LongSeq edges,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_faces(in CadUtility::LongSeq faces,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_edge_loops(in CadUtility::LongSeq edge_loops,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_shells(in CadUtility::LongSeq shells,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Entity Factory issue (Function 5)

  • Key: CAD-40
  • Legacy Issue Number: 4631
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    5. Function
    CadUtility::LongSeq index_oriented_faces(in CadUtility::LongSeq faces,
    in CadUtility::LongSeq vertices,
    in CadUtility::LongSeq vloops)

    Maybe instead of this, the description should be something like this:

    index_oriented_faces(in CadUtility::LongSeq faces,
    in CadUtility::BooleanSeq senses)?

    For what reason should you put the vertices and vloops in parameters?

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

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

Entity Factory issue (Function 4)

  • Key: CAD-39
  • Legacy Issue Number: 4630
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    4. Function
    CadUtility::LongSeq index_oriented_xxxxxxxx

    For functions which create oriented entities, boolean flags "sense" should be present in parameters, i.e. like BooleanSeq senses.

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

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

Entity Factory issue (Function 3)

  • Key: CAD-38
  • Legacy Issue Number: 4629
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    3. Function
    CadUtility::LongSeq index_shells (in CadUtility::LongSeq oriented_faces)
    raises (IncorrectIndex, CadUtility::CadError);

    The same situation. "In" parameter orieneted_faces should be CadUtility::LongSeqSeq, because shell is a set of faces.

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

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

Entity Factory issue (Function 2)

  • Key: CAD-37
  • Legacy Issue Number: 4628
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    2. Function
    CadUtility::LongSeq index_edge_loops(in CadUtility::LongSeq oriented_edges)

    Edge loop is described by list of edges, because of this, the "in" parameter oriented_edges should be CadUtility::LongSeqSeq.

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

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

Entity Factory issue (Function)

  • Key: CAD-36
  • Legacy Issue Number: 4627
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Function
    CadUtility::LongSeq index_faces(in CadUtility::LongSeq oriented_eloops,
    in CadUtility::LongSeq eloops, in CadUtility::LongSeq edges,
    in CadUtility::LongSeq vertex_loops, in CadUtility::LongSeq surfaces)

    Could you describe, please, the reason of presence of "eloops" and "edges" in the parameters?

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632

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

interface for STEP open shel

  • Key: CAD-35
  • Legacy Issue Number: 4595
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Suggest interface for STEP open shell, ie a collection of faces that do not enclose a volume.

  • Reported: CAD 1.0b1 — Fri, 5 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This functionality is available in the current CadGeometry::Shell interface.

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

Deletion of CadFourndation::Entity descendants

  • Key: CAD-34
  • Legacy Issue Number: 4573
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    Possible resolution:

    Add methods:

    interface CadSystem

    { void delete_model(in string modelname) raises (InvalidModel, PermissionDenied, CadUtility::CadError); // Removes model from CadSystem void delete_model(in CadMain::Model model) raises (InvalidModel, PermissionDenied, CadUtility::CadError); // Removes model from CadSystem }

    interface Model

    { exception EntityOutOfModel; void delete_entity(in long uid) raises (EntityOutOfModel, NotIndependent, UidUnsupported, PermissionDenied, CadUtility::CadError); // Removes ModelInstance, BrepEntity, Curve or Surface from the model void delete_entity(in CadFoundation::Entity entity) raises (EntityOutOfModel, NotIndependent, PermissionDenied, CadUtility::CadError); // Removes ModelInstance, BrepEntity, Curve or Surface from the model }
  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This is essentially the same issue as involved with 4571.

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

Entity.Position() returns PointStructure instead of TransformationStructure

  • Key: CAD-33
  • Legacy Issue Number: 4572
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    Replace
    CadUtility::PointStruct position () raises (CadUtility::CadError);
    // Returns a struct of the coordinates of a single, reference location on
    // the entity that should be unique relative to neighboring entities.
    method by
    CadUtility::TransformationStruct location () raises (CadUtility::CadError);
    // Returns a struct of the applied transformation, which represents
    // the location (position, turn, scale) of the entity according the global coordinates

    In that case, we will be able to refer the entity according any other entities.
    This method doesn't return the "last applied transformation", but "the superposition
    of all applied transformations". In that case, location of the entity in 3D space will be returned.

  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Duplicate

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

There is no way to delete any CadFoundation::Entity interface child.

  • Key: CAD-32
  • Legacy Issue Number: 4571
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    There is no way to delete any CadFoundation::Entity interface child.
    We shall add the possibility to delete:

    Model
    ModelInstance
    BrepEntity
    Curve
    Surface

  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

CadFoundation::Entity interface

  • Key: CAD-31
  • Legacy Issue Number: 4570
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    There is no "3D Location" function in Entity interface.
    There is only Entity.Position(), which returns PointStructure,
    but it is not enough to describe a 3D transformation.
    It's necessary to return TransofmrationStruct from such a function.
    It's necessary also to mention, that Entity interface has a method for
    transformation.

    However, if Position() has another goal, than 3D location of Entity, it
    shall be described in the document.

  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Surface.intersect_ray argument error

  • Key: CAD-30
  • Legacy Issue Number: 4566
  • Status: closed  
  • Source: Westinghouse Electric ( Jim Jones)
  • Summary:

    The 'intersection_parameters' argument in Surface.intersect_ray() must be type 'CadUtility::UvStructSeq' instead of 'CadUtility::DoubleSeq'.

  • Reported: CAD 1.0b1 — Thu, 13 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed.

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

CadSystem Properties issue

  • Key: CAD-29
  • Legacy Issue Number: 4564
  • Status: closed  
  • Source: Anonymous
  • Summary:

    In the CadServer interface we have the ability to inquire launch
    properties for the CadSystem, and then pass in a set of properties
    when we call connect() or connect_with_password().

    Once the CadSystem is running we do not have a way to query or
    change the properties.

    As an example - UG has a property for the search path for files.
    You can set this property when you initially start up the CadSystem.
    If it needs to be changed during a session the only choice is to
    shut down the CadSystem with disconnect() then call connect()
    again.

    Also, if you connect to an already running CadSystem you
    cannot determine what properties were used during the original
    connect().

    I think I would propose adding something like "get_properties"
    and "set_properties" for the CadSystem interface. These calls
    would basically allow a query and update of the properties
    provided to the CadServer via the connect() calls.

    CosPropertyService::Properties get_properties();
    void set_properties( in CosPropertyService::Properties props );

  • Reported: CAD 1.0b1 — Thu, 6 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    The proposed operations were added to the CadSystem interface.

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

I haven't found any way to create ModelInstance

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

    7. Creation of ModelInstances. I haven't found any way to create ModelInstance. And it's not explained in the specification.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Replace #include "CadFeature.idl with #include "CadFoundation.idl"

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

    6. #include list of CadGeometry module contain:
    #include "CadFeature.idl"
    that has to be replaced by #include "CadFoundation.idl".
    CAD Geometry never use features explicitly.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This is a good observation. The #include was modified.

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

Method names in topological entities are not everywhere unified

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

    5. Method names in topological entities are not everywhere unified. To return a single entity we use normally prefix get_entity.
    To return a sequence we use no prefix normally: for example

    Shell get_shell () raises (CadUtility::CadError);
    OrientedFaceSeq oriented_faces () raises (CadUtility::CadError);

    Not all method names in CadBrep module satisfy this rule.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    All operations that did not follow the standard naming procedure were changed.

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

how to add new topological entities to existing model with sharing of exist

  • Key: CAD-25
  • Legacy Issue Number: 4560
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    3. It is not clearly described in the specification document, how to add new topological entities to existing model with sharing of existing entities.
    Let's say we have 2 vertexes already created and we would like to add an edge.
    While implementing EntityFactory interface, a developer have to care about this sharing. Otherwise vertexes won't be shared.
    And from my point of view we have to speak about that in the document.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

method of CadMain::EdgeLoop has to be renamed

  • Key: CAD-24
  • Legacy Issue Number: 4559
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    OrientedEdgeLoopSeq edge_loop() raises (CadUtility::CadError); method of CadMain::EdgeLoop has to be renamed to
    OrientedEdgeLoopSeq oriented_edge_loop() raises (CadUtility::CadError);
    for unification.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    The operation is renamed.

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

we have to generalize is_manifold() methods in all BRep entities

  • Key: CAD-23
  • Legacy Issue Number: 4558
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    1. Perhaps we have to generalize is_manifold() methods in all BRep entities. I propose to have is_manifold() only in BrepEntity interface, but not in each interface. The only restriction is vertex, which can return anytime TRUE.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

adding an attribute to the entity group

  • Key: CAD-22
  • Legacy Issue Number: 4551
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Our entity groups in Cad Services don't have any form of an
    identifier or name that can be retrieved through the interface.
    The only returned data is either a list of entities in the group or
    the count. It makes it difficult to present this information to a
    user.

    We might consider adding an attribute to the entity group,
    however that means it gets inherited to the layer.

    readonly attribute string native_label;

  • Reported: CAD 1.0b1 — Thu, 30 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    A readonly attribute was added to the EntityGroup interface.

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

Section 3.4, Editorial

  • Key: CAD-21
  • Legacy Issue Number: 4548
  • Status: closed  
  • Source: NIST ( Mr. David Flater)
  • Summary:

    Section 3.4, Editorial: Although the description of interaction with
    PDM Enablers is fairly clear, a sequence diagram (or several, for
    the several cases) would increase the likelihood of
    interoperability.

  • Reported: CAD 1.0b1 — Mon, 20 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Appropriate sequence diagrams were added to the specification.

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

Sections 1.8, 2.8, 3.1, 3.2, Editorial

  • Key: CAD-20
  • Legacy Issue Number: 4547
  • Status: closed  
  • Source: NIST ( Mr. David Flater)
  • Summary:

    Sections 1.8, 2.8, 3.1, 3.2, Editorial: Compliance points / levels
    and optional interfaces are spread around the document in a way that
    would hamper formal claims of conformance.

  • Reported: CAD 1.0b1 — Mon, 20 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Support for STEP input / output?

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

    Support for STEP input / output?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Body.property_info, several values are calculated. What is the return accur

  • Key: CAD-18
  • Legacy Issue Number: 4543
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Body.property_info, several values are calculated. What is the return accuracy? Should a separate accuracy for each separate property be returned? Should accuracy be returned at all?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

BodyTessellationStruct issue

  • Key: CAD-17
  • Legacy Issue Number: 4542
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Should Shell.tessellation return a similar structure to Body.tessellation? Currently shell tessellation returns a FaceTessellationStructSeq while body tessellation returns a BodyTessellationStruct. Shell tessellation results are the only tessellation results that do not have an object reference to underlying topology. Rename BodyTessellationStruct to something like ConnectedFaceTessellationStruct?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

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

Model level parameters for geometry creation issue

  • Key: CAD-16
  • Legacy Issue Number: 4541
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Model level parameters for geometry creation. Should the model creation operation support new parameters?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. A Model creation operation was modified in the CadSystem interface.

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