User support list for MayaVi data visualization program ()

Michele Mattioni | 28 Dec 2011 11:24

What is the best way to tackle this two bugs

Dear Mayavi users,

I was wondering if you can replicate this two bugs or not with current master:

https://github.com/enthought/mayavi/issues/21
https://github.com/enthought/mayavi/issues/20

both bugs are 'regression' bugs. Everything was working before with
Mayavi 3.6.0.
The main trouble is that a program I wrote is using the Qt embedding
and the picker for the mouse, and these two bugs are stopping the
release of the new upcoming version.

https://github.com/mattions/neuronvisio/issues/34
https://github.com/mattions/neuronvisio/issues/32

I'm not familiar with Mayavi source code, however I could try to help
if you point me in the right direction!
Thanks!

Cheers,
Michele.

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev

(Continue reading)

headers

Gael Varoquaux | 3 Jan 2012 15:22

Re: What is the best way to tackle this two bugs

Hi Michelle,

Sorry for the slow reply.

On Wed, Dec 28, 2011 at 11:24:15AM +0100, Michele Mattioni wrote:
> I was wondering if you can replicate this two bugs or not with current master:

> https://github.com/enthought/mayavi/issues/21
> https://github.com/enthought/mayavi/issues/20

> both bugs are 'regression' bugs. Everything was working before with
> Mayavi 3.6.0.

It seems to me that the first one (#21) is really a bug due to a change
in VTK rather than Mayavi. Are you sure that with the same VTK version,
3.6.0 works. Anyhow, it should be fixed... Someone just needs to find
time.

The second bug (#20] should probably be reassigned to traitsui, as it is
really a problem in the image_enum_editor.py. By the way, you'll probably
find more traction to such emails on the enthought-dev, as this is where
both Traits and Mayavi developers (what's left of them) hang out.

> I'm not familiar with Mayavi source code, however I could try to help
> if you point me in the right direction!

Here are a few ideas to try and move the situation:

Bug #21: figure out which call in VTK has changed signature, and what is
the new signature. For this inspect the call stack using pdb to see where

(Continue reading)

headers

Michele Mattioni | 4 Jan 2012 16:25

Re: What is the best way to tackle this two bugs

Hi Gael,

thanks for the reply.

I've mailed also the enthough-dev list to see what is going to happen.
I've commented on both issues all the info I could have collected so far.

Cheers,
Michele.

On Tue, Jan 3, 2012 at 3:22 PM, Gael Varoquaux
<gael.varoquaux <at> normalesup.org> wrote:
> Hi Michelle,
>
> Sorry for the slow reply.
>
> On Wed, Dec 28, 2011 at 11:24:15AM +0100, Michele Mattioni wrote:
>> I was wondering if you can replicate this two bugs or not with current master:
>
>> https://github.com/enthought/mayavi/issues/21
>> https://github.com/enthought/mayavi/issues/20
>
>> both bugs are 'regression' bugs. Everything was working before with
>> Mayavi 3.6.0.
>
> It seems to me that the first one (#21) is really a bug due to a change
> in VTK rather than Mayavi. Are you sure that with the same VTK version,
> 3.6.0 works. Anyhow, it should be fixed... Someone just needs to find
> time.
>

(Continue reading)