[vtk-developers] vtkArrayExtents (and others) Python wrapping

[Eric E. Monson]

Thanks, David,

I'll take a look at it in the next day or two and let you know if I have any problems. I appreciate you addressing this so quickly.

Talk to you later,
-Eric


On Sep 14, 2010, at 9:27 AM, David Gobbi wrote:

> Hi Eric,
> 
> This morning I added some code that allows the python wrappers to
> resolve typedefs, so those missing vtkArray methods are wrapped again.
> Let me know if the new code works for you.
> 
>  David
> 
> 
> On Tue, Sep 7, 2010 at 7:47 PM, Eric E. Monson <emonson at cs.duke.edu> wrote:
>> On Sep 7, 2010, at 7:02 PM, Timothy Shead wrote:
>> 
>>> On 9/7/10 1:38 PM, David Gobbi wrote:
>>>> I'm fine with that.  Wrapper typedef support is something that I had
>>>> planned from the start, I just didn't expect that it would be needed
>>>> so soon.  What do you think of Eric's GetDimensionRange() method
>>>> suggestion?  I'd prefer that there are always named-method
>>>> alternatives to [ ] operator methods.
>>> 
>>> Makes sense, although I would strongly prefer vtkArrayExtents::GetExtent(...), for consistency with vtkArray::GetExtent(...), which returns the same value.
>> 
>> Ah, thank you -- I hadn't seen the vtkArray::GetExtent() option. I can get the values from that for now.
>> 
>> -Eric
>> 
>>