<br>
On 4/18/06, <b class="gmail_sendername">Marc Cotran</b> <<a href="mailto:marc@cotran.ca">marc@cotran.ca</a>> wrote:<div><span class="gmail_quote"></span><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
I see what you're saying... Of course you *could* keep track of your<br>actors in a "vtkActorToPigment" hash table. That way, when you pick you<br>would find out if your hash table has a pigment for the picked actor...
<br>This would avoid subclassing vtkActor - but I guess you really want to<br>subclass...</blockquote><div><br>
yes, I'd rather subclass.. pitty though.. even a single void* would have saved my soul.<br>
If only there was a way to attach arbitrary data to vtkObjects, I'd have my<br>
acme hash table in no time ;-)<br>
</div><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">gl!<br></blockquote></div>Thanks!<br><br>-- <br><a href="mailto:stoptv@gmail.com">
stoptv@gmail.com</a>