[vtk-developers] Text problems with vtkWindowToImageFilter::SetMagnification
Ken Martin
ken.martin at kitware.com
Mon Jan 20 11:31:47 EST 2003
Hello Prabhu,
I do not believe that RenderLargeImage supports any 2D actors and I
don't have any plans to add that functionality. However,
vtkWindowToImage does support them (and there is at least a minimal test
to verify this using a scalar bar actor). If WindowToImage is failing to
properly draw an Actor2D then there is a bug. I would be surprised if it
was failing with just a TextMapper since the ScalarBar uses them and I
know I have tested them a fair amount. Now the cursor3D class is a whole
different story. I've never tried that with the WindowToImage filter so
I wouldn't lay a bet on it working. Can you verify the problem with a
TextMapper using WindowToImage and send the script I'll try to fix it.
Thanks
Ken
> -----Original Message-----
> From: vtk-developers-admin at public.kitware.com [mailto:vtk-developers-
> admin at public.kitware.com] On Behalf Of Prabhu Ramachandran
> Sent: Sunday, January 19, 2003 4:22 AM
> To: vtk-developers at public.kitware.com
> Subject: [vtk-developers] Text problems with
> vtkWindowToImageFilter::SetMagnification
>
> hi,
>
> I just discovered a problem with text rendering when the
> vtkWindowToImageFilter is used with a magnification > 1. This also
> occurs when a vtkRenderLargeImage is used. The problem is
> particularly bad with the vtkCubeAxesActor2D where pretty much nothing
> shows up correctly. I also tested with a simple vtkTextActor. This
> does show up but the position naturally changes when the image is
> scaled up. Is this incorrect behaviour or to be expected? If so what
> should be done about it? It looks like the CubeAxesActor does not
> scale up properly along with the other actors. This is a problem when
> high res pictures are desired.
>
> I've attached a Python script that is adapted from
> Examples/Python/Rendering/RenderLargeImage.py that demonstrates the
> problem for the vtkCubeAxesActor and also with a vtkTextActor.
>
> I'm using:
>
> vtk version 4.1.1, vtk source $Revision: 1.1462 $, $Date: 2003/01/16
> 03:45:10 $ (GMT)
>
> I am not sure if this is fixed or is even related to Bill's error
> report a little earlier.
>
> Thanks.
>
> prabhu
More information about the vtk-developers
mailing list