| 00:25.39 | *** join/#stepcode konrado (~root@41.205.22.10) |
| 01:36.06 | konrado | Please I have posted some questions concerning STEP on the BRL-CAD and STEPcode mailing list but I have not gotten any replies. |
| 01:39.57 | konrado | I do not know if there is something I am not doing right, or was the message received as spam because I can see it on http://sourceforge.net/p/brlcad/mailman/brlcad-devel/ |
| 01:47.28 | starseeker | konrado: apologies - we've been rather busy lately |
| 01:47.41 | starseeker | I just responed to one STEP message - was that yours? |
| 01:47.48 | starseeker | responded rather |
| 01:48.30 | konrado | starseeker: thanks for the response |
| 01:49.48 | konrado | I have just tied the man command but I just got the response "No man page found for STEP" |
| 01:49.56 | starseeker | brlman STEP ? |
| 01:50.16 | konrado | yes |
| 01:50.21 | starseeker | do you have the latest sources compiled or are you working with an older release? |
| 01:51.35 | konrado | The copy I am using is about ten months old |
| 01:51.47 | starseeker | konrado: OK, if you can I'd try updating to the lastest |
| 01:51.53 | starseeker | the STEP man page is relatively new |
| 01:52.48 | starseeker | also, if you haven't started doing so already I'd take a look at the step-g importer code - take a simple STEP file from the web and follow it through in a debugger to see how the logic works |
| 01:53.33 | starseeker | there is a "dry run" option on the newer step-g builds that will do the structure walk without actually doing the conversions, if I recall correctly |
| 01:54.01 | konrado | I would try that |
| 01:54.40 | starseeker | konrado: that's really the best advice I have - there isn't a simple way to explain a lot of this stuff, the standard is just too large and uses too much weird terminology |
| 01:55.18 | starseeker | just walk through the working importer to see how it functions, and from there you'll get a sense of how the newer one will need to work |
| 01:55.43 | konrado | I tried working through by adding cout(print) statement within the code since I am not good with using a debugger |
| 01:56.15 | starseeker | konrado: ah. I suggest spending a little time getting familar with gdb - the code base is a bit large for cout |
| 01:56.45 | konrado | That is what I realized |
| 01:58.00 | starseeker | konrado: sounds like you've got the next steps in hand then - it really is just working with the code to get a handle on it, there aren't any shortcuts I know about |
| 02:06.51 | konrado | starseeker: I really appreciate the response. I just wanted to know if I am on the right track and find some better ways to get up to speed with STEP. |
| 05:45.34 | *** join/#stepcode d356__ (~d@50-90-234-94.res.bhn.net) |
| 12:16.30 | *** join/#stepcode AnxiousGarlic (~Fruit@130.225.98.198) |
| 18:32.55 | *** join/#stepcode alisha (~quassel@106.192.144.223) |
| 18:48.32 | *** join/#stepcode alisha (~quassel@101.60.226.127) |