Hi Brett, That is a bit of brute force (the public area of TGeo classes is a bit unlimited unfortunatelly so far). Doing that will permanently decouple some nodes during the session, will still keep the voxels (navigation optimizing structure - this might still fire-up an extra search - hopefully there is a protection there) and eventually leave you with a memory leak, but I agree you might get away with it if you need the feature that fast. Anyway, I will still implement it in a proper way. Regards, Andrei Brett Viren wrote: >Hi Andrei, > >Andrei Gheata writes: > > > > This is related to an old idea that we had on volume tracking attributes > > - as you are able to make volumes visible/invisible for visualization, > > to do the same related to tracking. I knew the problem will pop-up > > sooner or later. > >This does sound useful. I don't want to discourage you from >implementing it, but, I think I have found a solution to my problem. >For my purposes it seems I can prune everything below some particular >volume by calling TGeoVolume::ClearNodes() on it. So far, this seems >to work the way I expect so I think my immediate needs are met. > >Regards, >-Brett. > >
This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:06 MET