[vtk-developers] Python wrapped void pointers

David Cole DLRdave at aol.com
Mon Feb 23 19:41:22 EST 2015


So can callers now pass "_f02100_p_void" instead of the formerly
accepted "_f02100_void_p" ... ?

On Mon, Feb 23, 2015 at 5:09 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> This is a result of one of the bugs that I fixed during last year's
> hackathon:
>
> http://www.vtk.org/Bug/view.php?id=12098
> http://review.source.kitware.com/#/c/17351/
>
>
> On Mon, Feb 23, 2015 at 2:59 PM, David Lonie <david.lonie at kitware.com>
> wrote:
>>
>> A project I work on is facing a regression related to the
>> vtkRenderWindow::SetDisplayId(void*) method.
>>
>> It apparently used to work by passing a string similar to:
>>
>> '_f02100_void_p'
>>
>> as the argument, but now they're getting TypeErrors:
>>
>> TypeError('SetDisplayId argument 1: value is _f02100_void_p, required type
>> is p_void',)
>>
>> For context, the failure is happening here:
>>
>>
>> https://github.com/UV-CDAT/VisTrails/blob/cb2220ba88e957006c3dcc098ef29c5c08461117/vistrails/packages/vtk/vtkcell.py#L356
>>
>> It looks like the python wrappers might have changed how they handle the
>> void* type -- does anyone have an idea what's going on here?
>>
>> Thanks,
>> Dave
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtk-developers
>
>


More information about the vtk-developers mailing list