Ufuk,
In any case, both issues are now fixed in `master` and should be available
in the next release candidate.
Utkarsh
On Fri, Feb 17, 2017 at 12:05 PM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:
> Ufuk,
>
> I believe the issue you're running into is https://gitlab.kitware.com/
> pa
Ufuk,
I believe the issue you're running into is
https://gitlab.kitware.com/paraview/paraview/issues/17197, more so than the
one your pointed.
I have a fix for 17197 on the way:
https://gitlab.kitware.com/paraview/paraview/merge_requests/1393
Utkarsh
On Fri, Feb 17, 2017 at 4:39 AM, wrote:
>
Hi Ufuk,
I'm not sure if this fix will make it into the 5.3 release. We'll try but
we have a pretty hard deadline for the release.
As a workaround, while Trace is not capturing the movement the Python state
does. You can use that information to set the desired values in your
Catalyst Python scrip
Hi,
I was using Catalyst with 5.2 and the color bars are shown as tiny and
also misplaced when it is compared with ParaView output. I also checked it
with 5.3RC1 and the issue is still in there. So, is there any plan to fix
it in 5.3. There ware also discussion about it in the mail list and it
see
