Yes I will see of I can isolate it and upload a sample. After I posted I tried using topods-listofshape to hold the objects, and I got different (but still wrong) behavior. In that case I noticed that when the path is first created, I have a compound of wires, but then later the wires are gone and I have a reference to a compond that is empty.
Oddm On 2/15/10, Thomas Paviot <tpav...@gmail.com> wrote: > 2010/2/16 Dave Cowden <dave.cow...@gmail.com> > >> Ok, so after some debugging I have cornered my issue, I think. I believe >> that i've got some variation of the scoping issue happening compound wires >> that were valid and then stored in a python list later disappear. >> >> As i loop through building toolpaths, i basically do a pattern that looks >> like this pseudocode: >> >> toolpaths = [] >> >> for ( all slices and faces ) >> make toolpath >> toolpaths= [] >> >> for toolpath in toolpaths: >> exportToGcode(toolpath) >> >> >> when the toopath is created, i can display it and export it, but later on >> when i loop over all the paths, some of them have disappeared. >> >> >> I remember talking about this last year-- however I remember seeing some >> posts from Thomas about re-doing garbage collection. >> >> What should i be doing to make sure that the wires and such i create are >> retained till i dont need them any more? >> >> thanks.... >> > > Hi Dave, > > The behaviour you describe makes me worry, I'm gonna have a bad day ;') I > can't see exactly what's wrong with from your algorithm. I need to run a > python script see the issue by myself. Anyway, objects do *not* disappear (I > can not believe it), neither short life objects (like gp_*) or long life > ones (smart pointed objects like Handle_*). Can you reproduce the issue with > the smallest possible number of lines and share it so that we can help you? > > Thomas > _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
