Re: application

Hello Philippe,

Thanks for your answer, here:

• Code that do not work: When I use gApplication. Do I need to call anything else. Call a member of gApplication or something ?
• Code that works: I call 'new TApplication(...) inside my code and use that pointer instead of gApplication. The constructor complains, but it still give me a new instance and my program runs well.

thanks,

John Idarraga

On Wed, 2009-11-25 at 12:29 -0600, Philippe Canal wrote:
> Hi John,
>
> > I do so, and I get a valid pointer, but when doing this, my program crashes.
>
> I do not quite understand the code that works and the code that do not work.
>
> The unique TApplication object can (should) always be access via
> gApplication.
>
> Cheers,
> Philippe
>
>
> John Idarraga wrote:
> > Hello people,
> >
> > Little question. I am writing an application that is using the ROOT
> > library. I still want to run my library making instances of my objects
> > from CINT and steering the run from there. At some point I need to get
> > a handle on a TApplication object. Since I am not providing the 'main'
> > call of my application because I am running with CINT, that object
> > should already exist, right ? I see that ROOT has already instantiated
> > and object of the class TApplication and I can get a pointer to it
> > through the global gApplication pointer or through
> > gROOT->GetApplication(). I do so, and I get a valid pointer, but when
> > doing this, my program crashes.
> >
> > I couldn't do much with gdb to find out what was going on. But if
> > instead I try to build a new instance of TApplication myself, the
> > constructor of TApplication tells me "only one instance of TApplication
> > allowed", but still delivers me a new object and this one let me work
> > without crash. I am surely miss-understanding something here. Any
> > ideas ?
> >
> > thanks,
> >
> > John Idarraga
> >
> >
> >
>
Received on Wed Nov 25 2009 - 19:42:12 CET