create_nurbsurf_from_surf

[arenner]

I use this function to create a simple extruded surfaces from an arc. However, when I finish the the chook that creates this function, I cannot select any of the surfaces that were created with my mouse pointer in the graphical environment. I looked into the database and when I report it, it says "4 Surfaces" were created. But the rest of my surfaces are called "Trim Surfaces". Why can't I select the generic "Surfaces" type that were created by my chook? And, is there another function to create "trim surfaces" instead of the "create_nurbsurf_from_surf" function I'm using?

[Pete Rimkus from CNC Software Inc.]

arenner,

 

create_nurbsurf_from_surf() doesn't put the surface in the database. It needs to be followed up with a call to put_surf_in_db().

How are you defining the surface that's being passed into create_nurbsurf_from_surf()? Is it a DRAFT_SURF? a TABCYL_SURF?

Please note that making surfaces this way will not make trimmed surfaces - the result of calling create_nurbsurf_from_surf() and put_surf_in_db() will be an untrimmed NURB surface. There's probably no need to worry about trimming if they're simply extruded arcs.

[arenner]

I believe it is a TABCYL_SURF (dont' have the code in front of me right now). I wasn't aware of the put_surf_in_db(). I'm a little confused on why I need to put them in the database still when they show up with the "Report" function from the Level Manager. I will try this, but do not understand the benefit/use of a "trimmed" surfaces, feel free to explain if you don't mind:)

[arenner]

Actually, I got this to work. I had to put a rebuild_graphics in . Takashi I think sent me some of this code. As I mentioned, the surfaces show up in the database. That is because I used the "store_ent" and "draw_ent" functions. I'm not sure if this is a bad idea, and should be using something like put_surf_in_db instead? Either way, thanks for the input. If you have any explanation of trimmed surfaces, I'd definitely listen:) Thanks.

code:

---

 

surf.s.type = TABCYL_SURF;

memset(&e,0,sizeof(ent));

create_nurbsurf_from_surf(&surf, &e);

store_ent (&e, &e_ptr, ALIVE_BIT, extrude_color, main_level, main_attrib, &succf);

draw_ent(&e,e.color);

rebuild_graphics();

---

[Pete Rimkus from CNC Software Inc.]

arenner,

Glad to hear you got it working. put_surf_in_db() is simply a wrapper around store_ent() which accepts a 'surf_type' as input.

You shouldn't need the draw_ent() or the rebuild_graphics() - store_ent() does the 'draw' for you. Why did you feel they had to be added?

Trimmed surfaces are a type of surface which contain trimming data and a pointer to an untrimmed surface. If you don't have a real need yet to go there, don't worry about it.

[arenner]

Trimming Data? I guess that's a new one to me.

 

I'll try it with just the store_ent(). If I put just store_ent and draw_ent, then when my cursor moved over the newly created surfaces, they could not be selected. When I add the rebuild to the end of both of those functions, then I can select and highlight the surfaces. With either situation, the surfaces were reported as such in the Level Manager Report (in the database).

 

I'm wondering if the draw_ent requires the rebuild_graphics. So without the draw_ent function in there, maybe I will be able to select the surfaces after using only a store_ent.

[markov]

quote:

---

put_surf_in_db() is simply a wrapper around store_ent() which accepts a 'surf_type' as input.

---

Just an observation here: put_surf_in_db must be doing something else other than just being a wrapper. Like arenner noticed, surfaces created by store_ent are not selectable, while those created with put_surf_in_db are.

[markov]

After some additional experimentation, I found that put_surf_in_db sets the surface parameters I had missed originally, like curvatures and extents.