I realize that I am deviating somewhat from ROOT's primary intended use.
What I want to do is avoid having to rewrite my library of combinatorial
application classes to be ROOT/CINT-able, yet still capitalize on ROOT's
powerful graphical capabilities. I originally programmed some graphs into
my main(), but they soon grew so large that I felt a need to move them into
their own set of functions, to allow for easy mixing and matching.
Understanding that I may be abusing the ROOT way of doing things, do you
have any suggestions for wrapping a series of ROOT commands, including
creating a canvas, pads, and plots, into a function?
Any suggestions are greatly appreciated,
Matt
On Mon, 16 Nov 1998, Rene Brun wrote:
>Matthew R. Nelson wrote:
....
>> that I want plotted in various ways. Ideally, I would like to create a
>> new class that encapsulates these plotting routines. Besides the various
>> initializations required in the main() file, I would like all of the
>> ROOT functions handled by this class, including creating the canvas.
>>
>> Would this create any scoping problems for ROOT? Can I declare a canvas
>> inside a function? Do I need special declarations of the ROOT objects
>> (extern, etc.)? Are there any example applications someone could point me
>> to?
....
>Matt,
>I would suggest you have a look at the Root tutorials to get an
>idea of the intended use of the system.
>Masa has recently posted to this list the CINT STL restrictions.
>He is currently extending the support for STL. Vectors and strings
>should be supported if you use the latest version of Root 2.00/13.
>Masa will, may be, clarify my point.
>
>Rene Brun
>
>Rene Brun
-- ---------------------------------------------------------------------------- Matthew R. Nelson Dept. of Human Genetics University of Michigan http://www-personal.umich.edu/~ticul/ 4711 Medical Science II email: ticul@umich.edu Ann Arbor, MI 48109-0618 phone: (313) 647-3151 ----------------------------------------------------------------------------