By default your components starts in the "stopped" state, cf :
http://www.orocos.org/stable/documentation/rtt/v2.x/doc-xml/orocos-compo...

If you want to start unconfigured you have to precise this in the
TaskContext constructor :

class MyTask
: public TaskContext
<http://www.orocos.org/stable/documentation/rtt/v2.x/api/html/classRTT_1_1TaskContext.html>
{
public:
MyTask(std::string name)
: TaskContext
<http://www.orocos.org/stable/documentation/rtt/v2.x/api/html/classRTT_1_1TaskContext.html>(name,
*PreOperational*) // demand configure() call.
{
//...
}
};

Be also aware that some way of deploying may be done in such a way that the
components starts in a configured state (or even running state). For
instance kickStart() is doing this.

So in your case, as your component is in the Stopped state, the
isConfigured() is returning true as expected.

2013/7/17 <mirkodaniele [dot] comparetti [..] ...>

> Hi all,
>
> I realized that the isConfigure() method for every component
> always returns true, even if the component the configureHook()
> is never executed, and thus the component is not configured. This is also
> visible from the flag [S] close to the component name.
>
> Is it the correct behavior?
>
> Thank you,
>
> Mirko
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>