vtk-m/vtkm/rendering/AxisAnnotation.h
Robert Maynard ff687016ee For VTK-m libs all includes of DeviceAdapterTagCuda happen from cuda files
It is very easy to cause ODR violations with DeviceAdapterTagCuda.
If you include that header from a C++ file and a CUDA file inside
the same program we an ODR violation. The reasons is that the C++
versions will say the tag is invalid, and the CUDA will say the
tag is valid.

The solution to this is that any compilation unit that includes
DeviceAdapterTagCuda from a version of VTK-m that has CUDA enabled
must be invoked by the cuda compiler.
2019-04-22 10:39:54 -04:00

50 lines
1.6 KiB
C++

//============================================================================
// Copyright (c) Kitware, Inc.
// All rights reserved.
// See LICENSE.txt for details.
//
// This software is distributed WITHOUT ANY WARRANTY; without even
// the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
// PURPOSE. See the above copyright notice for more information.
//============================================================================
#ifndef vtk_m_rendering_AxisAnnotation_h
#define vtk_m_rendering_AxisAnnotation_h
#include <vtkm/rendering/vtkm_rendering_export.h>
#include <vtkm/rendering/Color.h>
#include <vtkm/rendering/Scene.h>
#include <vtkm/rendering/WorldAnnotator.h>
namespace vtkm
{
namespace rendering
{
class VTKM_RENDERING_EXPORT AxisAnnotation
{
protected:
void CalculateTicks(const vtkm::Range& range,
bool minor,
std::vector<vtkm::Float64>& positions,
std::vector<vtkm::Float64>& proportions,
int modifyTickQuantity) const;
void CalculateTicksLogarithmic(const vtkm::Range& range,
bool minor,
std::vector<vtkm::Float64>& positions,
std::vector<vtkm::Float64>& proportions) const;
public:
AxisAnnotation();
virtual ~AxisAnnotation();
virtual void Render(const vtkm::rendering::Camera& camera,
const vtkm::rendering::WorldAnnotator& worldAnnotator,
vtkm::rendering::Canvas& canvas) = 0;
};
}
} //namespace vtkm::rendering
#endif // vtk_m_rendering_AxisAnnotation_h