开云体育

There are several big expensive brokers that do trailing stops on the client, Cyber included. Don't assume ... Richard } I wonder how long before the API supports this. Does the trailing } stop

I recently forwarded a message from this list to IB management in hopes of eliciting a positive response. (I hope you don't mind, grozzie.) I'm including the response below, which was somewhat

Who said it wouldn't be adjustable? Yikes! Silly assumption. Richard } } I would never use this... I actually can't imagine using a trailing } stop without basing it on each stock's volatility.

I would never use this... I actually can't imagine using a trailing stop without basing it on each stock's volatility. I've been discouraged for years because no portfolio feature at the most

I wonder how long before the API supports this. Does the trailing stop sit on IB's servers, or is it implemented on the client? Scratch that last question... I am sure IB realizes how useless it

Trader Workstation Trailing Stop Orders and Island 1/10 Cent Order Entry You asked for it, and IB delivers. As of August 1st, you will be able to enter trailing stop orders with "Smart" order

croc, Does esignal have an API, like QCharts? Can you easily download historical intraday data? .. Dan

Hi, it seems, no one is using the ESignal Datafeed together with IB. I can only recommend it, as it's sometimes cheaper than QCharts. If you talk directly with a sales representative, they might

I am pleased to announce the "Open Source Trading Software" group for *Open* discussion of how to implement open source/free solutions for trading software. Special emphasis will be on automated

My expirience is, that it happens, but it happened only a few times. As you described in your first eMail with this topic, normally it is ok within a second, the events are just in the wrong

position creates an Does it do anything about the discrepancies, or just create a message ?

re- Well, it can be made to work, and like i pointed out in the prior message, if you can live without cross checks, there is always a way. I cant live without cross checks, and as I press on, i'm

I do it similar: 1. Manually check/correct open positions at startup (they a stored in a database and should be the same as yesterday evening) 2. Just track the status of orders while ignoring

In theory, this will work, provided there is never a communications hiccup. This is why i must reconcile positions and orders as a cross check. It's quite one thing to have an order entry front

Kind of depressing Grozzie....Programming is not difficult at all, just complex. And it is this sort of nonesense that makes it even more complex... What a bummer... They should just turn over all

Can you do the following: 1. Request open positions at startup 2. Just track the status of orders while ignoring position messages 3. Using the status of the orders, update your own internal list of

My first thought as I was reading your original post was to introduce a small delay in processing responses. I agree completely that the message order problem you have found is serious and needs

Total elapsed time of that sequence was just inder 1.5 seconds. I dont use the 'poll the socket on a timer' methodology that the sample code uses, I have a dedicated thread reading the socket from

grozzie How much time elapsed during this series of events? Kent

there are 2 reports (at least 50% of trades) sometimes even 3 (10% of trades). They contain the same info. I see this all the time in the demo. Lots of things reported twice, and once in a while,