> > Hard to advise on your class hierarchy when we don't really know what > you are trying to achieve, though... > Its only a couple of windows project the main opening window does the work, takes a set of parameters and runs the data algorithm.
once this has been ran the user can then choose to use the 'map data' mode this requires a new window with a couple of buttons and the number pad. both the windows have a save or load button also which opens a filebrowser and input etc. if i can get this simple functionality well organised then i can extrapolate it to adding more stuff as required. > Now, in the absence of any other info., it sounds to me like your top > level class is maybe wrong. It shouldn't contain a window unless all > it's children want to have their own window, I suggest. > I'd make the top level class only contain the parts that need to be > common, then create subclasses of that which, if necessary, add a window > object. This sounds like i maybe need to make FLUID classes inherit from my main class? there are a fair few functions and data to the main work class "DataGenerator" but no window creation code. these utilities need to be mostly available to any other windows as things develop. At present the FLUID class MainWindow is the superclass and contains only widget and window creation code. the DataGenerator class containing all the aforementioned utilities inherits from this. it invokes an instance of MainWindow DataGenerator::DataGenerator() : MainWindow() _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
