|
Hi,
yes, this is true and this issue has been discussed several times on this forum. The thing is that initially we had an idea to split order propagation chain into two layers. One, low layer, deals with execution reports and orders, and consequantly operates with partial fills and order quantities. The other, transaction and portfolio position layer, deals with transactions, which represent complete order fills. We though that such structure would simplify startegy development. Actually it does simplify strategy development (so that most of time you simply write HasPosition in your strategy entry and exit code and don't bother with partial positions/fills tracking) but on the other hand it turns out that this might lead to some sort of confusion that you've described in your post.
We will try to imporve this concept in a new version of the framework.
Cheers, Anton
|