Ignore:
Timestamp:
Aug 22, 2011, 2:15:12 AM (13 years ago)
Author:
ldelgass
Message:
  • Let graphics objects handle DataSet? cumulative range changes, track vectors as well as scalars, also supply cumulative ranges in setDataSet()
  • Be more consistent about naming enums and commands for vectors
  • Add constructor arguments to some graphics objects to speed initialization (eliminates some pipeline changes)
  • Apply a scale factor to glyphs based on cell sizes
  • Add line glyph shape
  • Don't delete ColorMaps? in use
  • Update graphics objects when a ColorMap? is edited
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/packages/vizservers/vtkvis/RpPolyData.cpp

    r2393 r2402  
    109109                // to get the grid boundary as a PolyData
    110110                vtkSmartPointer<vtkDataSetSurfaceFilter> gf = vtkSmartPointer<vtkDataSetSurfaceFilter>::New();
     111                gf->UseStripsOn();
    111112                gf->SetInputConnection(mesher->GetOutputPort());
    112113                gf->ReleaseDataFlagOn();
     
    121122        TRACE("DataSet is not a PolyData");
    122123        vtkSmartPointer<vtkDataSetSurfaceFilter> gf = vtkSmartPointer<vtkDataSetSurfaceFilter>::New();
     124        gf->UseStripsOn();
    123125        gf->SetInput(ds);
    124126        gf->ReleaseDataFlagOn();
Note: See TracChangeset for help on using the changeset viewer.