Change-Id: Ie7fe5b7de4e6849047d4bc24622a5b0686815204

Restored testing of the parametric functions in computational geometry.

Change-Id: Idd9979b07ec539bc14865259f2db2368558d9f2d

This adds new API to a few of the vtkAlgorithm sub-classes which
allows the user to decide what level of floating-point precision
they want for the vtkPoint's object in the output data set. By
default these algorithms will output points with a precision equal
to that of the input data set. Alternatively the user may instruct
the algorithm to always use single-precision or double-precision.

Change-Id: I1c6b8ca854ff8da1bae5415e2d4c33fbfbaf1153

Change-Id: I4e0b20f8fa4ecb1c2b89a7b44e87c2a1fce7ae39

The main change is to remove the use of vtkTemporalDataSet and move
the support of multiple temporal data sets from the execution
pipeline to filters. To be specific,

- Before, a filter can request objects from multiple time steps by
  setting the key UPDATE_TIME_STEPS to a vector of doubles; the
  resulting objects get wrapped by the pipeline into a single
  vtkTemporalDataSet object.

- After, a filter can only ask for a single time step from the
  pipeline by setting the key UPDATE_TIME_STEP to a single double.
  The "wrapping" no longer happens. If a filter want to request
  multiple time steps, it needs to either inherit from
  vtkMultiTimeStepAlgorithm or use the CONTINUE_EXECUTION to loop the
  upstream pipeline and store the data from each iteration.

The following key changes/constants are backward incompatible:

vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEPS(() ->
   vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP((),
   vtkMultiStepAlgorithm::UPATE_TIME_STEPS()

vtkStreamingDemandDrivenPipeline::PREVIOUS_UPDATE_TIME_STEPS() ->
  vtkStreamingDemandDrivenPipeline::PREVIOUS_UPDATE_TIME_STEP()

deleted: vtkCompositeDataPipeline::REQUIRES_TIME_DOWNSTREAM()

depreicated: VTK_TIME_EXTENT

Change-Id: I635b6401ae4f0a7ea7c4b5c466ced40ee75963c7

A Get* method should not return an object that needs to be deleted by
the caller; instead, the object must be passed as parameter.

Change-Id: I0925efe7c476d8d59dc049e9709e261041cdbfba

Factored the vtkStandardNewMacro into a VTK_STANDARD_NEW_BODY macro and
a vtkStandardNewMacro. Also introduced vtkObjectFactoryNewMacro and
vtkAbstractObjectFactoryNewMacro in order to replace the functionality
present in some of the hard coded factories remaining from before VTK
modularization.

The vtkObjectFactoryNewMacro does what the vtkStandardNewMacro did
previously (and will continue to do if the VTK_ALL_NEW_OBJECT_FACTORY
option is turned on) - use the object factory override of the new method
of the class. The vtkAbstractObjectFactoryNewMacro will attempt to
return a class from the vtkObjectFactory::CreateInstance method, or
return NULL if there are no overrides, i.e. the behavior of the
vtkGraphicsFactory which is necesasary for abstract base classes like
vtkRenderWindow.

The VTK_ALL_NEW_OBJECT_FACTORY method allows VTK to be compiled with the
previous behavior of all New methods using the object factory. A new
static method was added to vtkObjectFactory largely for pragmatic
reasons - all of those implementations already include vtkObjectFactory
but not vtkDebugLeaks and so this reduces the change necessary to still
work with VTK_DEBUG_LEAKS when that option is on.

Change-Id: I06f713d70fc6d97ae086186c424a78f524592a4d

New data types were added and the datastructures not updated correctly. Fixed
that.

Change-Id: I951d947f6f51a1f9ad9a5133f3c7d7ad8647f25d

Use size_t for memory buffer sizes and vtkTypeInt64 for file positions
and offsets exposed in header files.  Use vtkTypeUInt64 for sizing and
indexing of whole data.  The latter will be necessary to read small
portions of data requiring 64-bit indexes on 32-bit architectures.
Use std::streampos for stream seek operations but avoid exposing it
in header files because its type can vary on some platforms depending
on preprocessor definitions for large file support.

Change-Id: I5c6eb335fb2415de652f012fbf34e2f2952e443a

Recent commit 122b241e (Define vtkIOStream(Pos|Off) as portable
std::stream(pos|off), 2012-05-04) added these for portability but the
standard types are available everywhere now that we support only
standard streams.  We can use std::stream(pos|off) directly instead.

Recent commit 6d2b9838 (vtk(Input|Output)Stream: Use appropriate types
in API, 2012-05-04) exposed std::streamoff (through vtkIOStreamOff) in
the public interface of vtkInputStream and vtkBase64InputStream.  In
order to present a consistent public interface use vtkTypeInt64 instead
because std::streamoff varies on some platforms depending on large file
support preprocessor definitions.

Change-Id: I8d2003a353e6cb7f010be631daf4e234eeec678b

Remove test for VTK_USE_ANSI_STDLIB and assume availability.  VTK no
longer supports C++ compilers without standard streams.  Define
VTK_USE_ANSI_STDLIB if VTK_LEGACY_REMOVE is OFF so applications that
test for it see the definition.

Change-Id: Ief0c47e8f720754db1916a96f6ed012aa0d8555e

Replace vtkIdType overloads of Get(Scalar|Vector)Attribute and
SetVectorAttribute with overloads for 'long long' and '__int64'.
When VTK_USE_64BIT_IDS is enabled one of them will match vtkIdType.
Remove unused SetIdTypeAttribute method.

Change-Id: I9af7138cd6bed68b035c2c8764f4bf2a46e39214

This adds back the off screen render window, as well as the optional
linking to OSMesa from the normal vtkXOpenGLRenderWindow.

Change-Id: I88d53e05efeae21efb898abcc39127b3f20dc7ef

Add the appropriate BTX ETX comments

Change-Id: I666cd03f889ea26908370d54df6fdee1e937cb01

I am excluding these methods from the test because they manufacture a new
list, which the smoke test doesn't know it should manually delete.

I believe a proper fix is to rename these methods because GetX in VTK implies
an accessor behavior.

Change-Id: Ib2aad1a9965e0eeeccec70a3cfb5fd55c2111d96

Remove use of old CMakeBackwardCompatibilityC variables:

 CMAKE_USE_PTHREADS
 CMAKE_USE_SPROC
 CMAKE_HP_PTHREADS
 CMAKE_USE_WIN32_THREADS
 CMAKE_NO_STD_NAMESPACE
 CMAKE_ANSI_FOR_SCOPE

Use of these was originally removed by

 commit fe401e0f (Remove old CMakeBackwardCompatibilityC thread options, 2012-02-23)
 commit e56a7eb9 (Drop workaround for no std:: namespace, 2012-02-23)
 commit ff74963a (Drop workaround for non-ANSI 'for' scope, 2012-02-23)

but accidentally restored by modularization.  Drop use of the variables
again.  The thread variables in particular interfere with the thread
library selection done by the top-level CMakeLists.txt file.

While at it, drop unused computation of VTK_USE_OPENGL_LIBRARY from
Common/Core.  Its value is hard-coded in Rendering/OpenGL when the
module is enabled.

Change-Id: Ife7730fbfe32c51f0c431d440935636b2bb34c39

This will handle buffers as large as the architecture can fit in memory.
It also will not switch with VTK_USE_64BIT_IDS.

Change-Id: I9a0f946f6e2a9d4b019b30309bc95bed69ae1e7d

Change-Id: I05d5b39ca3b8ed6deac9df84a69eade08fe1f104

vtkExtentTranslator is needed by vtkDataSet so move into that module

Change-Id: I5a20b2d292a327c8f965234b964d7193d80899ac

These types will be useful to handle stream position and offset values
of the same range as supported by the streams library.

Change-Id: Idfdf43ba84a3de831f81d73bd315f8167fb6cf61

Since the transition away from CVS and commit ecbbf7f7 (Remove
vtk(Cxx|Type)RevisionMacro, 2010-05-19) the per-file revisions reported
by vtkObjectBase::(CollectRevisions|PrintRevisions) have not been
implemented.  Drop these methods.  Define associated macros

  vtkExportedTypeRevisionMacro
  vtkTypeRevisionMacro
  vtkCxxRevisionMacro

to have no extra effects and only when VTK_LEGACY_REMOVE is OFF.
When VTK_LEGACY_REMOVE is OFF drop the PrintRevisions special
case from wrapping.

Change-Id: Idf543e405762c12777e4b83044d73f666b12e213

Change-Id: I557bcc04b090c737925044bff44533cb09a0bf2e

In pre-modular VTK, there used to be a Kit_WRAP_HEADERS variable
that listed config headers and other headers that did not contain
any class definitions, but which included important constants that
we wanted to wrap in python.

When Kit_WRAP_HEADERS was removed, these headers had to be included
in Module_SRCS in order to be wrapped by python, but then certain
tricks were needed to exclude them from e.g. java.  This commit
moves these headers back to HDRS, and then passes the HDRS to the
various wrappers and allows them to decide what to do with them.

Change-Id: Ieef0a7a42ab7ac0248f3635c6b460e5c08a418d4

Change-Id: Ie2fa2289cbc1e37e06a2ebc8877c6a6c7a3a3877

Change-Id: I4a33c10b1d29e3a0543c8cc759ed8a484b1c2988

Also improved documentation as this code becomes increasingly
complex

Change-Id: If39b01b73256bd638341b785cc4f065e9184550f

Change-Id: Ie083fbb5c371270c0260b868b67b9440d1853387

Change-Id: I289dae775066d8bcc3846dcff3e0ae75fcd6a337

Change-Id: I85c632c47cb4e41a3b76699d5bd268e26e78c4e3

Change-Id: I337eabe2854293fec60391af0ba7a8ef09b22541

Move VTK_(MAJOR|MINOR|BUILD)_VERSION out of "CMakeLists.txt" into
dedicated file "CMake/vtkVersion.cmake".  Move the preprocessor macros
from "vtkConfigure.h" to new configured header "vtkVersionMacros.h".
This avoids rebuilding everything when the version number changes.
Include the new header from the old location to provide the macros for
compatibility unless VTK_LEGACY_REMOVE is ON.

Define the BUILD version to be a date during development and the patch
level for releases (or during preparation of one as we are currently).
The CMake package version file (VTKConfigVersion.cmake) already does
this so make the C++-presented version consistent with it.  Add a
"CMake/vtkVersion.bash" script to help a nightly robot update the build
version when it is a date.  This replaces KWSys DateStamp for VTK.

Compile the wrapping parser with only the major and minor version number
components instead of the full version number.  This avoids causing a
full rebuild of all wrappers whenever the build version component
changes.  The wrapper only needs the version to provide its --version
option anyway.

Teach the documentation generation scripts to extract the VTK version
numbers from the new version file.  Drop the separate revision file
infrastructure because everything is now in one version file.

Also remove unused file CMake/VTKVersionMacros.cmake.

Change-Id: If988b32c738e6161237f7e3edaff49e75cb15b25

Change-Id: If0c0031d30f2b4a96d3e085861ed515110664b33

Philippe Pébay authored Apr 18, 2012 and Charles Law committed Apr 19, 2012

Change-Id: Id1dccd68bb37eaf6a5587bd3d1b4390932a6fa6a

Philippe Pébay authored Apr 18, 2012 and Charles Law committed Apr 19, 2012

Change-Id: I80be11dcb89e0a8f9cb66e8a228981d2a17787f5

Philippe Pébay authored Apr 17, 2012 and Charles Law committed Apr 19, 2012

Change-Id: Id6424bde7b30a224bf006e849c0ff60741bbc54a

Philippe Pébay authored Apr 17, 2012 and Charles Law committed Apr 19, 2012

Change-Id: I09b4bb0f74d2311ca1044b3d290da053a434a5d5

The method 'void GetPoint(vtkIdType, double x[3])', which is supposed
to be threadsafe, called the un-threadsafe method
'double * GetPoint(vtkIdType)'. I reversed the relationship of the
methods to make the former method actually threadsafe. Also, I replaced
the static variable that held the point location in the non-threadsafe
method with a member variable.

Change-Id: I44b79521a265aefdf9b54794f95be63f6c89c256

The VTK_ABI_IMPORT macro tells us *how* to import a symbol known to be
in a shared library, not *whether* it is in one.  It is not meant for
direct use and doing so tries to dllimport symbols from static libraries
on Windows.

Teach VTK_AUTOINIT to declare <mod>_AutoInit_(Construct|Destruct)
without any export/import markup.  The symbols are already exported
where they are defined.  Since they are not data symbols the linker will
resolve them in either a static library or dll import library
automatically.

Change-Id: I9939c6ed5946e8413fb6a9f3987b159e0d943530

Change-Id: Ia106a52b4680bee16f9dd6e28896c8cd3a92e4bf

Change-Id: I3e23ce741fd696a8e25bd69eb069acc8998db73b