| 00:26.31 | mpictor | starseeker: I created https://github.com/stepcode/stepcode/issues/251 for this |
| 00:26.44 | mpictor | s/this/your edge loop problem |
| 00:27.09 | mpictor | can you give me an instance that exhibits the problem? |
| 01:15.27 | starseeker | mpictor: it may not be necessary |
| 01:15.58 | starseeker | I can still do so if you like, but I found what is either a work-around or the "correct" approach... |
| 01:16.29 | mpictor | oh ok |
| 01:16.41 | starseeker | mpictor: do you have a BRL-CAD build? |
| 01:16.55 | mpictor | I did; I don't think I do at the moment |
| 01:17.28 | starseeker | It's the new g-step tool - I'm programmatically creating STEP geometry in src/conv/step/ON_Brep.cpp at the moment |
| 01:17.50 | mpictor | ok, I'll look at it - but not tonight |
| 01:17.51 | mpictor | is about to sign off |
| 01:17.58 | starseeker | cool - thanks! |
| 01:18.03 | mpictor | np |
| 01:18.26 | starseeker | I'll put together the detailed illustration tomorrow - bit tired myself |
| 01:19.56 | mpictor | cool! |
| 01:21.02 | mpictor | btw, if you run into null stuff in the future it may be because of an incomplete copy constructor or assignment operator |
| 01:22.19 | mpictor | issues 238, 239 if you haven't seen them already |
| 01:23.23 | mpictor | branch mp/STEPattr_ctors is a work in progress for 238 |
| 01:23.37 | mpictor | ttyl |
| 03:52.07 | *** join/#stepcode kesha_ (~kesha@14.139.122.114) |
| 04:09.15 | brlcad | kesha_: so still need to clean up installing the stepcode headers properly in that merge before we can migrate to brl-cad's step importer -- let me know when you have that all sorted out (remember to test install on your end) |
| 09:50.59 | *** join/#stepcode kesha_ (~kesha@14.139.122.114) |
| 14:32.51 | *** join/#stepcode kesha_ (~kesha@14.139.122.114) |
| 15:00.04 | *** join/#stepcode kesha_ (~kesha@14.139.122.114) |
| 18:01.48 | *** join/#stepcode kesha_ (~kesha@14.139.122.114) |
| 20:24.43 | *** join/#stepcode mpictor (~mark@2601:d:b280:b5:d63d:7eff:fe2d:2505) |
| 22:20.09 | starseeker | mpictor: any idea how to create a STEPcomplex entity in C++? |
| 22:21.18 | starseeker | mpictor: trying to create the context object for a step file, like (for example) #166 in http://www.steptools.com/support/stdev_docs/stpfiles/ap203/block.stp |
| 22:21.44 | starseeker | it's not clear to me how to programmatically create the object that will write that out |
| 22:45.24 | mpictor | oops, sorry I missed your question starseeker |
| 22:45.39 | mpictor | (and from the log, I guess I missed a q the other day as well) |
| 22:46.04 | mpictor | I had to figure out how to create STEPcomplex's for lazy loading |
| 22:47.23 | mpictor | src/cllazyfile/sectionReader.cc:306 |
| 22:51.24 | mpictor | you have to pass an array of char* containing the names of the types composing the STEPcomplex |
| 22:55.56 | starseeker | looks like the terminating condition isn't right in entnode.cc |
| 22:56.12 | starseeker | at least, per the example, a '0' string should terminate things |
| 22:56.25 | starseeker | or a null |
| 22:58.20 | starseeker | tries the '*' char... |
| 22:58.38 | starseeker | ah, bingo |
| 22:58.44 | starseeker | mpictor: cool, thanks! |
| 22:58.59 | mpictor | np |
| 22:59.06 | mpictor | what were you doing differently? |
| 22:59.11 | starseeker | we should probably update the example in the NEWS file... |
| 22:59.27 | starseeker | the example in NEWS terminates with a '0' |
| 22:59.54 | starseeker | plus I fed it upper case strings at one point... |
| 23:00.15 | starseeker | once it dawned on me that a STEPcomplex was what I needed... |
| 23:00.40 | starseeker | now I just need to figure out how to address and manipulate the individual components of the complex |
| 23:02.47 | mpictor | http://stepcode.org/doxygen/class_s_t_e_pcomplex.html |
| 23:03.06 | mpictor | _attr_data_list is a std::vector<void*> |
| 23:03.15 | mpictor | not sure what it holds |
| 23:03.23 | mpictor | maybe application_instances |
| 23:03.35 | mpictor | s/vector/list |
| 23:04.23 | starseeker | eeep |
| 23:05.09 | mpictor | yea |
| 23:05.22 | starseeker | well, our step-g importer unpacks it somehow |
| 23:05.41 | mpictor | or maybe in the STEPattributeList it inherits |
| 23:06.03 | starseeker | ah yeah, it's an SDAI_Application_instance isn't it... |
| 23:06.41 | mpictor | I finally scrolled far enough into NEWS to find the example you spoke of |
| 23:06.48 | starseeker | heh |
| 23:06.54 | starseeker | yeah, it's an oldie |
| 23:07.05 | mpictor | I bet that got broken when SCLstring was replaced with std::string |
| 23:07.27 | starseeker | nods - also is an api for const char **, which is probably the easiest to use |
| 23:08.52 | starseeker | will try populating this beast tomorrow - will need a fair number of additional supporting objects to get it right - but closing in on generating something that can be read back in as a valid step file |
| 23:09.44 | mpictor | cool! |
| 23:10.10 | starseeker | then I can start chasing down all the inevitable places where I got the geometry info messed up :-P |
| 23:10.48 | starseeker | calls it a night |
| 23:11.31 | mpictor | something I've wanted to do, but never got around to, is to add support to treg for creating complex instances |
| 23:12.16 | mpictor | then generate random-but-valid instances and try to break other parts of STEPcode |
| 23:12.22 | mpictor | night! |