[prev in list] [next in list] [prev in thread] [next in thread] 

List:       orocos-dev
Subject:    [Orocos-Dev] [Bug 158] addPeer connection direction
From:       peter.soetens () fmtc ! be (peter ! soetens () fmtc ! be)
Date:       2006-08-22 17:07:37
Message-ID: 200608221453.k7MErccd006979 () pc00155 ! site04 ! wtcm ! be
[Download RAW message or body]

For more information about this bug, visit
     <http://www.fmtc.be/orocos-bugzilla/show_bug.cgi?id=158>

A comment was added:


------- Comment #8 from peter.soetens@fmtc.be  2006-08-22 16:53 -------
(In reply to comment #7)
> 
> Most of the times we want to connect data flow between components and not the
> execution flow.
> Execution flow is mostly needed for the scripts. So i think for most examples
> connecting data flow is enough and splitting the connections of data and
> execution flow would make sence.

Well, let's see if this works...

$ svn commit -m"Fix for bug #158:addPeer connection direction:
* addPeer and connectPeers only setup \"Execution Flow\"
* connectPorts is used to setup \"Data Flow\", ie connect data ports.
"
Sending        current/include/ScriptingAccess.hpp
Sending        current/include/TaskContext.hpp
Sending        current/src/TaskContext.cxx
Transmitting file data ...
Committed revision 5574.


-- 
(this mail is best viewed with a fixed font)
Configure bugmail: http://www.fmtc.be/orocos-bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[prev in list] [next in list] [prev in thread] [next in thread]