INTRODUCTION
Overview
Download and Install
Quick Start
Documentation
Publications

NONFRAMEWORK CODE
Driver Interfaces
Drivers
Libraries
Utilities

FRAMEWORK CODE
Interfaces
Components
Libraries
Utilities

Full Software Listings

DEVELOPER
Tutorials
Examples
Dev Guide
Dashboard

PEOPLE
Contributors
Users

SourceForge.net Logo
Project
Download
Mailing lists

 

         

orcaice::Application Class Reference

Similar to Ice::Application, plus some Orca-specifc stuff. More...

#include <application.h>

List of all members.

Public Member Functions

 Application (orcaice::Component &component, Ice::SignalPolicy policy=Ice::HandleSignals)

Detailed Description

Similar to Ice::Application, plus some Orca-specifc stuff.

Typical usage:

int main(int argc, char * argv[])
{
    MyComponent component;
    orcaice::Application app( component );
    return app.orcaMain(argc, argv);
}
Author:
Alex Brooks
See also:
Service, Component

Constructor & Destructor Documentation

orcaice::Application::Application ( orcaice::Component component,
Ice::SignalPolicy  policy = Ice::HandleSignals 
)

Will start the component when main is called.

The flag installCtrlCHandler determines whether the Ctl-C handler is installed. By default it is and the handler destroys the communicator. This triggers component shutdown, if and only if the application is blocked in waitForCommunicatorShutdown(), i.e. if Communicator::start() returns control to application. Most console components should do that.

GUI components implemented in Qt are a notable exception. A Qt app::exec() called in Communicator::start() does not return. For such components set installCtrlCHandler=false and remember to call Communicator::destroy() or Communicator::shutdown() before returning from Component::start().


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

Webmaster: Tobias Kaupp (tobasco at users.sourceforge.net)


Generated for Orca Robotics by  doxygen 1.4.5