[mv2] behavior of surface module (contours enabled) and multiscalars v

headers fred | 17 Apr 2007 01:06

fred a écrit :
> Prabhu Ramachandran a écrit :
>> There was a tricky bug that I think I've fixed in SVN.  Please try
>> again.
> Great !
> Tons of thanks (I really need this trick to work 
Hi,
I'm back on this topic because I still have some issue, sorry 

I put data here (3,6 MB): http://fredantispam.free.fr/output.vti

and attached a simple example code.

I have 3 data, raw, filtered, residue in output.vti VTK XML file.

Could you try the attached script, please ?

Once python script launched, begin to show scalar bar.

Raw is the first data displayed.

1) WarpScalar + PolyDataNormals filters enabled

I this case, changing from raw to filtered or residue data updates the 
scene,
that's ok.

But as you have 2 modules managers, only the first is changed.
So as I enabled the color bar of the second module (because only the 
second MM handle data),
data name of the colorbar is not updated to the right name.

2) WarpScalar + PolyDataNormals filters disabled (commented)

In this case, as you have only one MM, data name of the colorbar is 
updated to the right name
when you change from raw to filtered or residue data. That sounds good.
By the way, the displayed data are not updated this time.

Cheers,

PS: VTK 5.0.2 from etch, mv2 #11063

--

-- 
http://scipy.org/FredericPetit

Re: [mv2] behavior of surface module (contours enabled) and multiscalars variable...