Mark Beall

Reported issues: 0

04:32 pm ITAPS iRel: RE: Changing from iRel_NOTEXIST: The reason for having the NOTEXIST state is for implementations to be able to have relations where they only provide ...

10:52 am ITAPS iMeshP: RE: 2 fundamental questions about iMeshP: Tim Tautges wrote:
> Hi all,
> Jason and I sat down and talked about iMeshP today, and we came away with two fund...

12:58 pm ITAPS iRel: RE: Replacing iRel_BOTH with "recursive": Tim Tautges wrote:
>
> Recall that a relation with a BOTH type on a side means that both the Sets and Ents on that...
09:56 am ITAPS iRel: RE: Replacing iRel_BOTH with "recursive": I'm completely missing something since I don't understand how the word "recursive" applies here.

10:03 am ITAPS iMesh: RE: iBase_CreationStatus in iMesh_createEnt: Tim Tautges wrote:
> The mesher didn't fill in the hole; the hole is still there topologically, it just has zero a...

06:51 pm ITAPS iMesh: RE: iBase_CreationStatus in iMesh_createEnt: Mark Miller wrote:
> Tim Tautges wrote:
> > So, just for grins, I created a model with cubit that looked like this:...
02:53 pm ITAPS iMesh: RE: iBase_CreationStatus in iMesh_createEnt: Mark Miller wrote:
> Mark Beall wrote:
> > I think that, if the application is worried about creating duplicate, it...
02:50 pm ITAPS iMesh: RE: iBase_CreationStatus in iMesh_createEnt: > I think that if the function fails (returns error code other than iBase_SUCCESS) then it should have create no en...
01:37 pm ITAPS iMesh: RE: iBase_CreationStatus in iMesh_createEnt: I think that, if the application is worried about creating duplicate, it should check if the entity is a duplicate be...

05:49 pm ITAPS Specification #193: Should we remove iBase_NO_MESH_DATA?: Simmetrix is in the process of updating our interface to the 1.2 release. Will keep you posted.

Also available in: Atom