[Octave-patch-tracker] [patch #8943] object class "light" for lighting effects on patches and surfaces

[Dan Sebald]

Follow-up Comment #35, patch #8943 (project octave):

I think this may have introduced an FLTK bug by calling an OpenGL routine
outside of an instantiated Fl_Gl_Window.  See here:

https://savannah.gnu.org/bugs/index.php?48669#comment10

I'm not sure how C++ orders initialization of something like


OpenGL_fltk (int xx, int yy, int ww, int hh, double num)
    : Fl_Gl_Window (xx, yy, ww, hh, 0), number (num), renderer (),
      in_zoom (false), zoom_box ()


but maybe if renderer() is moved inside of the constructor function it would
work.

I have another unrelated question.  Initialization of num_lights was removed
from before the loop, i.e.,:


-  // Start with the last element of the array of child objects to
-  // display them in the order they were added to the array.
-
-  num_lights = 0;


but it is still incremented somewhere within the loop.  How does one know that
the member variable num_lights has been initialized?  Or is the idea simply to
push num_lights as high as possible?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8943>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/