---

VisCoreContent Class Reference

Content proxy to create framework visualisation core. More...

#include <VisFramework/VisFrameworkBase/interface/VisCoreContent.h>

Inheritance diagram for VisCoreContent:

List of all members.

Public Member Functions
	VisCoreContent (IgState *state)
	Initialise the Framework event data proxy.
Private Member Functions
	IG_DECLARE_STATE_ELEMENT (VisCoreContent)
void	init (void)
	Actual (in-main-thread) initialisation.

---

Detailed Description

Content proxy to create framework visualisation core.

Definition at line 16 of file VisCoreContent.h.

---

Constructor & Destructor Documentation

VisCoreContent::VisCoreContent

(

IgState *

state

)

Initialise the Framework event data proxy.

Definition at line 24 of file VisCoreContent.cc.

    : VisContent (state, s_key, MAIN_THREAD,
                  lat::CreateCallback (this, &VisCoreContent::init))
{}

---

Member Function Documentation

VisCoreContent::IG_DECLARE_STATE_ELEMENT

(

VisCoreContent

)

[private]

void VisCoreContent::init

(

void

)

[private]

Actual (in-main-thread) initialisation.

Instantiates the FW EDM main program.

Definition at line 32 of file VisCoreContent.cc.

References ASSERT, DBSPlugin::get(), LFfwvis, LOG, VisContent::state(), and GsfMatrixTools::trace().

{
    LOG (0, trace, LFfwvis, "VisCoreContent::init()\n");

    // Bootstrap EDM main program.  It won't start yet, it will get
    // kicked by studio just before it goes into the event loop.  Qt
    // event loop will run in the studio once we return.
    //
    // We have two coordinated threads.  The current (= main) thread
    // runs the studio and the Qt event loop.  #VisMainProgram runs
    // the EDM main processing loop (#EventProcessor), which pumps
    // events as quickly as it can.  We hold the event loop using
    // #VisQueueProcessor as long as we have interest in the event.
    // The stepping through the events is managed via the menus and
    // control panels owned by the content proxies installed in this
    // doc.
    //
    // The application exit is coordinated as follows.  If the Qt
    // application quits, we tell #VisQueueProcessor to quit, which it
    // does by throwing an exception understood by the framework
    // #EventProcessor.  If the framework event loop exits before Qt
    // app, it tells the Qt app to quit.  Note that both can quit
    // roughly at the same time and the quit of one always causes of
    // quit of the other, so there is some amount of (safe) overlap.
    
    ASSERT (! VisMainProgram::get (state ()));
    new VisMainProgram (state ());

    ASSERT (! VisQueueProcessor::get (state ()));
    new VisQueueProcessor (state ());

    // FIXME: Block GUI until VisQueueProcessor gets an event: create
    // a global Qt event filter on the qApp (QObject::installFilter()
    // on qApp with another QObject with it's eventFilter() looking at
    // them), eating away all mouse clicks, keyboard events (and
    // drag/drop -- what happens when drag -> drop and we eat the
    // mouse release?  do we event get the release?  or do we get
    // a real drop event, which we should eat?)

    // FIXME: All this requires certain amount of defensiveness -- we
    // don't want to be left with the filter if the Framework thread fails
    // to start as expected.

    LOG (0, trace, LFfwvis, "VisCoreContent::init() done\n");
}

---

The documentation for this class was generated from the following files:

• VisFramework/VisFrameworkBase/interface/VisCoreContent.h
• VisFramework/VisFrameworkBase/src/VisCoreContent.cc

---