[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vtk-developers
Subject:    [vtk-developers] VTK's #define policy?
From:       "Dean Inglis" <dean.inglis () on ! aibn ! com>
Date:       2003-03-18 16:08:24
Message-ID: JNEGLEGOHCAPDKMPALHIKEAECDAA.dean.inglis () on ! aibn ! com
[Download RAW message or body]

Hi all,

I have been implementing a number of widgets lately
that rely on an external vtkPlaneSource to tag onto:
e.g., ruler widget, rectangular ROI widget, (vtkSplineWidget
is one in VTK).  These make use of the (same) following #defines in
their respective headers:

#define VTK_PROJECTION_YZ 0
#define VTK_PROJECTION_XZ 1
#define VTK_PROJECTION_XY 2
#define VTK_PROJECTION_OBLIQUE 3

Should these be placed in a common shared location?
Furthermore, most widgets have something like:

//BTX - manage the state of the widget
  int State;
  enum WidgetState
  {
    Start=0,
    Moving,
    Scaling,
    Spinning,
    Outside
  };
//ETX

Would it be advantageous/more efficient/cleaner to put one
enum ivar in vtk3DWidget.h ?

Dean


[prev in list] [next in list] [prev in thread] [next in thread]