If a stock changes name, and changes symbol, all historical data prior to the date of change appears to be lost or unaccessible. The new symbol does not have old data and the old symbol is invalid. Where'd the data go?
Thanks for the timely response, I look forward to using this functionality In my view, being able to get a year of 1s data across an index is especially relevant if you want to use IB for everything, rather than to gradually migrate to competing products.
Not a bug but I would like to know what week expiry the options I have in account window under contract description are. The ES options, for example, say march expiry but there are five march expiries.
Is there a way to save trend lines on charts? I draw the lines and click save settings but it will not save, am I missing something? Thanks.
TWS chart bug started by upgrading form TWS 933.5 to TWS 935.3. My TWS main page window and TWS chart windows are sized and positioned on my monitor screen so they overlap with a portion of each TWS window shows at all times. This allows me to mouse click on the visible part of any window to bring that window to the front on top of other TWS windows. My two charts are 2 day line charts with the volume panel at the bottom. BY upgrading form TWS version 933.5 to 935.3, the following undesirable bug action resulted: When my mouse pointer sweeps (not clicked) and touches any part of the data plot line on one of my line charts or the mouse pointer touches a volume bar, the chart jumps to the front of all other TWS windows. This unintended undesirable action is very debilitating. If this is a new feature added to TWS, there needs to be a way to disable the feature.
Since I upgraded from TWS 932.4 to the latest standalone version (938.1), I noticed a significant increase of memory consumption. I run TWS as an API for Multicharts 64 on a Windows 7 64 Bit workstation. With around 50 charts of IB tick data open in MC 64, memory consumption is constantly increasing during operation. After some hours of operation, memory usage reaches several GB until TWS does not react to inputs any more. Has anybody experienced the same issue?
I don't have similar reports plus, you cannot have TWS consume more than 1Gb (it is configured not to go over it) - are you running a custom configuration? Please submit your logs via ctrl-alt-H (please put there "Att: Dennis" and PM me your user name so I can look them up and see what's going on; PM me any other info you think might be relevant for me reproducing it. Thanks.