Anyone else having this problem with the very latest release? If you adjust the columns in the "Executions" window it won't save them...not only will in not save them, but with *every single execution* it moves them back to the default position. I keep my execution window very small for screen reasons and I open up only the columns that I need to see. Each time I execute it readjusts the column widths to a size that is so small I can't even see the details of the trade I just made. JB
Ok folks -- answered my own question: If you drag the columns around with the mouse they don't stay put. if you use the menu command -- File/Customize... and rearrange them with the provided interface they will remain. JB
Just got the standalone version of 735g up and running. Looks very nice. One comment though. On the executions page, in the "Time" column, I'd love to have an option to list the time without the date, and also in local time. Thanks, 99
Def, I installed the latest version 735g, and it still has the same problem with the buy/sell/cancle/connection color boxes being the pastel shades of the colors that should be there. This is when clicking on a buy or sell and geting the dropdown order line. Tried it on two differant computers with differant vid cards- same problem. None of the previous versions ot TWS had this problem. It is caused by the highliting of the order line itself. If i enter two or more sells/buys, the order line that is not highlited has the correct colors. I hope IB can fix this. Vid cards are appian, and ati98, win 2000, and win98. Thanks, flier
735g seems to have introduced some really nasty bugs with respect to hot keys and order line management. - When there's more than one order line opened from the same market data line, an order line is moved to the bottom of all order lines when the order is submitted. This is very confusing behavior and what's even worse the order line loses focus so it has to be reselected with the mouse before any further hotkey actions can be applied. - When there's a partial execution on an order TWS shifts cursor focus to the limit price input field. When subsequently an attempt is made to change the price using hotkeys, the characters corresponding to the hotkeys are input into the price field screwing up the order. I'm downgrading to an earlier version until these problems are resolved. Dave
With the latest edition a problem has come back that I thought had been rectified. If it bring up a buy or sell order and adjust the price, following which I select the order as a stop order, the price resets. For example, if XYZ has a bid at $25 and I click the bid the order will come up as sell @$25. But I want to sell on stop at $25.50 so I adjust the price to this value. I then chage the order from limit to stop and the price resets to $25. This was the way it worked months ago, but then a change was made so that selecting the order as a stop order did not reset the price. Now it does again, so one has to be careful to select "stop" before adjusting the price, not after. Can't see why it should only work this way and it can lead to submission of erroneous orders from the unobservant who do not notice the price resetting.
dufferdon, got some feedback on your post. "The reason is as follows. Now that we support stop limit orders from the main window, each order has a stop price and a limit price that is stored separately (and they are displayed in separate columns). Changing the limit price does not affect the stop price, and vice-versa. The simple solution is to always set the order type before adjusting the price." hope this clears things up.
1) Basket Orders. According to the user's guide, you can create a basket file either by using the TWS ("automatically"), or by simply using a text editor and writing out each line ("manually"). When I attempt to use a manually-created basket file, TWS prompts me for the "program trading flag." I am not prompted for this on basket files created automatically. The user's guide has the following list of flags: A Agency single order P Principal U Program order, index arb, for other agency Y Program order, non-index arb, for other agency Why am I only prompted for this on manually created files? I've compared a manually-created file with the file resulting from creating it within the TWS, and they are identical. What is the default flag used by automatically-created baskets? Any way to avoid being asked when submitting manually-created baskets? 2) Funds requirement. It appears to me that when an order is placed, IB checks that you have enough money to cover the trade by: (# of shares) * (market price) Ignoring margin for the moment. Why isn't it figured as: (# of shares) * (order price) As an example, at one point I submitted each of the following two orders, each one being the only open order when submitted: Buy 160 MSFT $64 Buy 10000 CSCO $1 The MSFT order was accepted, CSCO was not. The reason given for the CSCO rejection was "equity must exceed margin". In a long session with IBhelp, the person claimed that (#shares * order-price) was what IB used, but could not explain why the CSCO order was rejected. The help-person had several helpful ideas ("CSCO is not trading at $1!", "We think because you entered the order at $1, the system views it as unmarginable"), none of which support his claim that (shares * orderprice) is used. 3) OCA orders. I've already mentioned this to def, and he said he would pass it along, but if more interest is shown it might speed the programmers along. I would like to see a new order type that is basically an OCA order that is dependent upon the $-value spent. So, order(s) in the group are filled until the total amount paid reaches a specified limit, at which any remaining orders are cancelled.
Def, here's some more information concerning the bugs that have been introduced with version 735g that cripple hot key functionality. The first problem with order lines jumping around on submission seems to be due to TWS sorting all order lines by limit price that are attached to a particular market data line whenever any of those orders is submitted. This non-sensical behavior even includes the leftovers from already executed orders that remain on screen for a few seconds. The second problem with the keyboard focus being set to the limit price field thus making all hot keys unusable seems to be triggered whenever there's a partial execution or an order transmission (in the case of multiple order lines). I wish IB's programmers would take the time to actually test new versions before releasing them. Even superficial usage testing would have turned up these annoying bugs.
I have seen many different and contraddictory opinions on the isssue of the odd lot order with IB. Does anybody know exactly how it works? Can you trade orders of 123 shares, for example?