| New Feature Requests » Close by ticket # Jan 12, 2009 @ 09:55 AM (Total replies: 11) | |||||
|
I was just looking for additional functionality, just so that I wouldn't need to the custom API myself. At this time I have built workarounds combining the Excel DDE and some basic Excel programming. This leaves me with one small additional request however. That is: Please add to the Excel DDE the possibility to pass order release and cancel times for orders executed via Excel, just as they are possible for most order types directly inside OEC. |
|||||
| New Feature Requests » Close by ticket # Jan 03, 2009 @ 11:41 AM (Total replies: 11) | |||||
|
> Unfortunately, we do not have this feature scheduled for development in the near future, so you have to implement it yourself for now. Ehhh, ok. But how do you suggest I do that? I am a trader and market researcher not a computer programmer. > It sounds very similar to the Order.Comments property - is there anything that prevents you from using it? No, but from what I can tell it doesn't do me any good, for two reasons, with both reasons rendering each other mutually moot. 1) I can't tailor it's content. I trade some 20 markets, with at least two strategies each, using primarily OSO orders, with the second O being an individually managed trailing stop to the entry order. This can make for +100 working and held orders. It says OSO in the comments column for all of them, and as far as I can tell I can't change that. 2) Once an entry order is executed into an open position and "moves" to the open position window there is no comment possibility at all. The original entry order has lost the connection it originally had to the attached OSO trailing stop. With some 100 orders and with a need to keep track not only of the P/L for the markets but also for the P/L for the strategies and all market-strategy combos this quickly becomes rather messy with a HUGE INCREASED risk for human errors, and about two extra hours in back-office work a day, in the administration of it all. The main point is that it is paramount for a larger-scale, multi-strategy trader to keep track of both ends (entry and exit) of his trades as one unit. Connecting trades via order number (the original request in this thread) would be one way to approach that and simplify the daily activities for the trader, a better way would be to allow the trader to pass some kind of flag/comment/remark of his own choosing. This seems to me a very rudimentary thing that all traders could benefit from and demand and it boggles my mind there is no e-trading software providing it. That said I use OEC because it still has better OSO capabilities than for example PATS and TT. Even so, take a look at, for example, the FXCM currency trading platform to see how they are connecting OSO orders for the entire life span of the trade. They too are lacking a "sticky" comments feature, but everything else is very intuitive and user friendly. Thanks for reading this far, /Thomas Stridsman |
|||||
| New Feature Requests » Close by ticket # Dec 31, 2008 @ 07:29 PM (Total replies: 11) | |||||
|
Besides that doesn't matter either. When all is said and done the outcome is still the same, so you could make this a feature that runs locally on the client end to help the client keep track of his individual trades. On that theme I would also like the possibility to pass a comment with my trades, that also only needs to be stored locally, which would help me keep track of which strategy generated a particular trade and which of my exits that should correspond to it. Seems pretty uncomplicated to me, no? |
|||||
| New Feature Requests » Close by ticket # Dec 31, 2008 @ 07:13 PM (Total replies: 11) | |||||
|
Well, then your average accounting method isn't particularly well suited to your clients' needs, so as this is a forum for "New feature requests" I ask you to work on changing that instead of just saying it isn't possible. |
|||||
| New Feature Requests » Close by ticket # Dec 31, 2008 @ 04:16 PM (Total replies: 11) | |||||
|
Why? There is no reason for why you shouldn't be able to let me view the entry and exit pairing according to what fits my needs the best, no matter whether you are actually executing FIFO or not... |
|||||