Keyboard Shortcuts
Likes
- Ibcalpha
- Messages
Search
Re: how to start LIVE trading ??
Hi Richard, thanks for responding.? I looked at the log file and saw the problem.? I was editing the wrong config file, so that's why it keep starting 'paper'.? I updated the correct file, and now it works.? Not sure if you have plan to do this, but it would be great to have video walk thru so that newbies like me can just watch it and avoid these rookie mistakes and you don't have to keep answering the same questions. Just a thought.? Thanks again for your help.?
|
Re: how to start LIVE trading ??
开云体育Reply to this with your IBC logfile attached. And I mean attached, don’t quote the logfile in your reply text. Also include the whole file, not just extracts from it. ? By the way, you can also set the trading mode in the relevant start script, though it’s best not to. So make sure that if you have it set in both places, the setting is the same. ? Also, what do you mean ‘Login is the same for paper and live’? At least the user ids must be different, and I’d recommend using different passwords. ? Richard ? ? ? From: [email protected] <[email protected]> On Behalf Of linkblock123
Sent: Saturday, January 27, 2024 3:41 PM To: [email protected] Subject: [ibc] how to start LIVE trading ?? ? Hi I am able to login with paper trading. Now I went to config.ini file and changed?TradingMode=live instead of 'paper'.? Didn't change anything else. Login is the same for paper and live. But when I run StartTWS, it is still open paper trading in TWS, not live account.? Please help. Thanks.? |
how to start LIVE trading ??
Hi I am able to login with paper trading. Now I went to config.ini file and changed?TradingMode=live instead of 'paper'.? Didn't change anything else. Login is the same for paper and live. But when I run StartTWS, it is still open paper trading in TWS, not live account.? Please help. Thanks.?
|
Re: Error: Could not find or load main class ibcalpha.ibc.IbcTws
开云体育The log file shows that iBC is supposedly installed in C:\IBC, but in fact it simply isn’t there. ? You need to copy the IBC.jar and version files from the zip file into that folder. ? Richard ? ? From: [email protected] <[email protected]> On Behalf Of Michael Acharjee
Sent: Sunday, December 17, 2023 6:37 PM To: [email protected] Subject: [ibc] Error: Could not find or load main class ibcalpha.ibc.IbcTws ? Hi All, ? |
Re: Notice pop-up on TWS start
Thanks for your answer and your detailed explanation.
I suspect the reason you keep seeing the message is that you aren’t clicking the OK button, or perhaps not exiting cleanly from TWS. So try doing a full logon and a tidy shutdown, and you should never see this message again (until IBKR announces another new API thing). I’m clicking on the OK button every day, I see it after every automatic restart. And any restart, stop/start that I might do So here’s a question: are you actually using TWS properly, ie fully logged in with your live or paper-trading account? If so, I really don’t understand how you can be seeing this message, and you would need to take that up with IBKR. Well, I would say that I’m using it properly. Taking into account that is launched in a container and managed by IBC, but yes. If you have been using it properly logged in, you’ll probably have noticed that once login is complete, other dialogs are also displayed, such as the ‘Welcome’ dialog that is displayed to new users, and others that I noticed yesterday when running TWS 10.26 on a ‘virgin’ computer. IBC doesn’t handle any of these, because they either only appear once, or a means is provided via the UI to prevent them being shown again; and also because IBKR keeps changing them! In general, IBC doesn’t handle things that are easily dealt with once-and-for-all by the user, unless they are also shown by the Gateway: the Gateway is a different case, because it is likely that there will be no user present to deal with unexpected dialogs. For example there are commercial operations that use Docker images which contain Gateway ‘as installed’, ie exactly as Gateway is set up when first installed, with no user customisations: this is not really viable with TWS, because it is so much noisier, and I’m not prepared to put in the programming time to handle that frequently-changing noise Another thing: I suggest that you set StoreSettingsOnServer=yes in your config.ini. This will ensure that your settings at the end of a TWS run are automatically uploaded to IBKR, and then reinstated when you run it again. Note that this only happens of TWS is closed tidily: if the IBC/TWS process is terminated (eg via a kill command), the settings are not uploaded. So any changes during that session are lost. You can also configure SaveTwsSettingsAt in config.ini to have your settings uploaded to IBKR on a specified schedule, though this is not really very useful. I haven’t set it on config.ini, but it’s set on my config. This is actually working, because my layout and settings are identical to those I have on my PC installation. I will try with SaveTwsSettingsAt I just started TWS on my PC, and I don’t see any message, back to the container and there it is. It’s lost somewhere in between. Alternatively you have to make sure that the TWS settings directory (which is /config/tws_settings according to your logfile) is on a Docker volume that will be persisted between runs: my knowledge of Docker is limited so I can’t advise you on that. Also note that TWS only saves its settings at a tidy exit or on the SaveTwsSettingsAt schedule.Yes, `/config` directory is persistent. Thanks for your help. In any case this is just a small annoyance. I’m not sure there’s a lot more I can say, but feel free to ask any further questions about this. |
Re: Notice pop-up on TWS start
开云体育Ok, let me start by stating that I will NOT enhance IBC to automatically handle this pop-up. I’ll try to explain why. ? The message is just one example of something that appears when IBKR introduces a new TWS version with API-related changes that they think need to be brought to the user’s attention. It looks like the message is displayed the first time the user runs that new version (or a later version if they never install the one that introduced the new features), and is never shown again (provided the user clicks the OK button and lets TWS exit normally). The fact that it has been displayed seems to be recorded against the user’s account on the IBKR server. It doesn’t matter whether the user uninstalls that version, or installs it on a computer where it has never been installed before: once the user has been shown the message they will never see it again. This probably explains why I have been totally unable to see this message with TWS 10.26, no matter where I install it: I had previously been using TWS 10.25, and earlier versions, and probably saw the message when I started using the one that first produced it. ? I suspect the reason you keep seeing the message is that you aren’t clicking the OK button, or perhaps not exiting cleanly from TWS. So try doing a full logon and a tidy shutdown, and you should never see this message again (until IBKR announces another new API thing). ? So here’s a question: are you actually using TWS properly, ie fully logged in with your live or paper-trading account? If so, I really don’t understand how you can be seeing this message, and you would need to take that up with IBKR. ? If you have been using it properly logged in, you’ll probably have noticed that once login is complete, other dialogs are also displayed, such as the ‘Welcome’ dialog that is displayed to new users, and others that I noticed yesterday when running TWS 10.26 on a ‘virgin’ computer. IBC doesn’t handle any of these, because they either only appear once, or a means is provided via the UI to prevent them being shown again; and also because IBKR keeps changing them! ? In general, IBC doesn’t handle things that are easily dealt with once-and-for-all by the user, unless they are also shown by the Gateway: the Gateway is a different case, because it is likely that there will be no user present to deal with unexpected dialogs. For example there are commercial operations that use Docker images which contain Gateway ‘as installed’, ie exactly as Gateway is set up when first installed, with no user customisations: this is not really viable with TWS, because it is so much noisier, and I’m not prepared to put in the programming time to handle that frequently-changing noise ? Another thing: I suggest that you set StoreSettingsOnServer=yes in your config.ini. This will ensure that your settings at the end of a TWS run are automatically uploaded to IBKR, and then reinstated when you run it again. Note that this only happens of TWS is closed tidily: if the IBC/TWS process is terminated (eg via a kill command), the settings are not uploaded. So any changes during that session are lost. You can also configure SaveTwsSettingsAt in config.ini to have your settings uploaded to IBKR on a specified schedule, though this is not really very useful. ? Alternatively you have to make sure that the TWS settings directory (which is /config/tws_settings according to your logfile) is on a Docker volume that will be persisted between runs: my knowledge of Docker is limited so I can’t advise you on that. Also note that TWS only saves its settings at a tidy exit or on the SaveTwsSettingsAt schedule. ? I’m not sure there’s a lot more I can say, but feel free to ask any further questions about this. ? Richard |
Re: Notice pop-up on TWS start
开云体育Thanks for the logfile. It explains my confusion. ? It throws up a few things that I’ll need to explain and discuss with you, and that may take some time. So this is just an initial response to let you know I’m on the case. ? More later. ? Richard ? ? From: [email protected] <[email protected]> On Behalf Of Gonzalo Saenz
Sent: Tuesday, December 5, 2023 7:48 PM To: [email protected] Subject: Re: [ibc] Notice pop-up on TWS start ? Hi, ? Please find attached the log file. ? There are few things that you should know, as they might be important ?
? Thanks for your help ? ? |
Re: Notice pop-up on TWS start
开云体育Hi,Please find attached the log file. There are few things that you should know, as they might be important
Thanks for your help
|
Re: Notice pop-up on TWS start
开云体育This is very strange. I can’t understand why your setup should behave differently from mine. We’re both using the same versions of TWS and IBC. My original check was on my paper-trading account, but it’s the same with my live account: no sign whatsoever of that dialog. ? In order to gather more information, please do the following: ?
? LogStructureScope=unknown LogStructureWhen=open ?
? Richard |
Re: Notice pop-up on TWS start
开云体育Thanks for your answerOn 3 Dec 2023, at 19:42, Richard L King <rlking@...> wrote: I see it when I start IBC/TWS
Same here, running?10.26.1h and IBC 3.18
No this is only on start up, and after the daily restart. Basically when I start IBC, it starts TWS, performs login, and clicks on all the pop-ups/settings, however that pop-up is left??袄冲(ツ)冲/? In any case, it seems to me that you shouldn't be seeing this message if you This is what I get in the log file, I can see that states “detected dialog entitled: IBKR Trader Workstation” which match the screen shoot that I shared, but I don’t know if it’s the same one or not 2023-12-03 18:35:02:901 IBC: detected frame entitled: Login; event=Lost focus 2023-12-03 18:35:02:901 IBC: detected frame entitled: Login; event=Deactivated 2023-12-03 18:35:02:901 IBC: detected frame entitled: Interactive Brokers; event=Activated 2023-12-03 18:35:02:903 IBC: detected frame entitled: Interactive Brokers; event=Focused 2023-12-03 18:35:03:492 IBC: detected frame entitled: Login; event=Closed 2023-12-03 18:35:03:492 IBC: detected frame entitled: Login; event=Closed 2023-12-03 18:35:11:709 IBC: detected dialog entitled: IBKR Trader Workstation; event=Opened 2023-12-03 18:35:11:712 IBC: detected dialog entitled: Trader Workstation Configuration; event=Opened 2023-12-03 18:35:11:713 IBC: Got config dialog from future 2023-12-03 18:35:11:713 IBC: Got config dialog from future 2023-12-03 18:35:11:713 IBC: Got config dialog from future 2023-12-03 18:35:15:490 IBC: Setting Auto restart time 2023-12-03 18:35:15:634 IBC: Auto restart time already set to 08:24 AM 2023-12-03 18:35:15:635 IBC: Setting ReadOnlyApi 2023-12-03 18:35:15:728 IBC: Read-Only API checkbox is already set to: false 2023-12-03 18:35:15:746 IBC: 'Bypass Order Precautions for API Orders' is already selected 2023-12-03 18:35:15:746 IBC: 'Bypass Bond warning for API Orders' is already selected 2023-12-03 18:35:15:746 IBC: 'Bypass negative yield to worst confirmation for API Orders' is already selected 2023-12-03 18:35:15:746 IBC: 'Bypass Called Bond warning for API Orders' is already selected 2023-12-03 18:35:15:746 IBC: 'Bypass "same action pair trade" warning for API orders.' is already selected 2023-12-03 18:35:15:746 IBC: 'Bypass price-based volatility risk warning for API Orders' is already selected 2023-12-03 18:35:15:746 IBC: 'Bypass US Stocks market data in shares warning for API Orders' is already selected 2023-12-03 18:35:15:747 IBC: 'Bypass Redirect Order warning for Stock API Orders' is already selected 2023-12-03 18:35:15:747 IBC: 'Bypass No Overfill Protection precaution for destinations where implied natively' is already selected 2023-12-03 18:35:17:076 IBC: Configuration tasks completed 2023-12-03 18:35:17:076 IBC: Click button: OK 2023-12-03 18:35:17:477 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed 2023-12-03 18:35:17:562 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Lost focus 2023-12-03 18:35:17:575 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deactivated 2023-12-03 18:35:17:825 IBC: detected dialog entitled: IBKR Trader Workstation; event=Activated 2023-12-03 18:35:17:827 IBC: detected dialog entitled: IBKR Trader Workstation; event=Focused 2023-12-03 18:35:17:844 IBC: detected dialog entitled: IBKR Trader Workstation; event=Lost focus 2023-12-03 18:35:18:195 IBC: detected dialog entitled: IBKR Trader Workstation; event=Focused 2023-12-03 18:35:18:197 IBC: detected dialog entitled: IBKR Trader Workstation; event=Lost focus 2023-12-03 18:35:18:197 IBC: detected dialog entitled: IBKR Trader Workstation; event=Focused 2023-12-03 18:35:18:198 IBC: detected dialog entitled: Trader Workstation Configuration; event=Closed 2023-12-03 18:35:24:180 IBC: detected dialog entitled: IBKR Trader Workstation; event=Lost focus 2023-12-03 18:35:24:180 IBC: detected dialog entitled: IBKR Trader Workstation; event=Deactivated 2023-12-03 18:35:24:181 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Activated 2023-12-03 18:35:24:189 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Focused 2023-12-03 18:35:24:193 IBC: detected dialog entitled: IBKR Trader Workstation; event=Closed 2023-12-03 18:35:35:667 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Lost focus 2023-12-03 18:35:35:679 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deactivated 2023-12-03 18:35:38:287 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Activated 2023-12-03 18:35:38:295 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Focused 2023-12-03 18:35:53:485 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Lost focus 2023-12-03 18:35:53:507 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deactivated 2023-12-03 18:35:53:519 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Iconified 2023-12-03 18:35:53:525 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed 2023-12-03 18:50:02:662 IBC: detected frame entitled: Connecting to server...; event=Opened 2023-12-03 18:50:02:663 IBC: detected frame entitled: Connecting to server...; event=Activated 2023-12-03 18:50:02:664 IBC: detected frame entitled: Connecting to server...; event=Focused 2023-12-03 18:50:17:497 IBC: detected frame entitled: Starting application...; event=Lost focus 2023-12-03 18:50:17:497 IBC: detected frame entitled: Starting application...; event=Deactivated 2023-12-03 18:50:17:497 IBC: detected frame entitled: Starting application...; event=Closed 2023-12-03 18:58:23:782 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deiconified 2023-12-03 18:58:23:810 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed 2023-12-03 18:58:23:865 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Activated 2023-12-03 18:58:23:873 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Focused 2023-12-03 18:58:27:166 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed 2023-12-03 18:58:48:586 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Lost focus 2023-12-03 18:58:48:597 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deactivated 2023-12-03 18:58:48:618 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Iconified 2023-12-03 18:58:48:641 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed 2023-12-03 19:17:14:267 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deiconified 2023-12-03 19:17:14:284 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed 2023-12-03 19:17:14:319 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Activated 2023-12-03 19:17:14:335 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Focused 2023-12-03 19:17:19:676 IBC: detected dialog entitled: IBKR Trader Workstation; event=Opened 2023-12-03 19:17:19:823 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Lost focus 2023-12-03 19:17:19:828 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deactivated 2023-12-03 19:17:19:831 IBC: detected dialog entitled: IBKR Trader Workstation; event=Activated 2023-12-03 19:17:19:834 IBC: detected dialog entitled: IBKR Trader Workstation; event=Focused 2023-12-03 19:17:23:688 IBC: detected dialog entitled: IBKR Trader Workstation; event=Lost focus 2023-12-03 19:17:23:690 IBC: detected dialog entitled: IBKR Trader Workstation; event=Deactivated 2023-12-03 19:17:23:690 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Activated 2023-12-03 19:17:23:702 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Focused 2023-12-03 19:17:23:708 IBC: detected dialog entitled: IBKR Trader Workstation; event=Closed 2023-12-03 19:17:28:701 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Lost focus 2023-12-03 19:17:28:708 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Deactivated 2023-12-03 19:17:28:725 IBC: detected frame entitled: U111111111 Interactive Brokers; event=Iconified 2023-12-03 19:17:28:735 IBC: detected frame entitled: U111111111 Interactive Brokers; event=State changed Thanks for your help Thanks. |
Re: Notice pop-up on TWS start
Please can you explain when you're seeing this message.
toggle quoted message
Show quoted text
I have the latest version of TWS 10.26.1h installed, and I don't see this message at all, regardless of the API precautions settings. Does it only occur when you place a bond order? If so, can you give details of the relevant contract, as I have no knowledge of bonds. In any case, it seems to me that you shouldn't be seeing this message if you have set the relevant API precaution setting. And which setting is it referring to? - there isn't a 'Bypass bond disclaimer for API orders' setting. Thanks. Richard -----Original Message----- |
Re: IBController suddenly stops working
开云体育{Please in future can you attach log files rather than include the contents in your post. Then I can open it in a text editor, which makes it much easier to search, compare with other logs, reply to the post, etc. Thanks.] ? The problem is that there is an ‘autorestart’ file, which IBC has found at ? C:\Jts\1023\iajkokhhkfokpbefffeopnfbopjjbaikdonojggf\autorestart ? This file is created by TWS when it autorestarts. Its existence makes IBC believe that TWS is auto-restarting, and in this case IBC doesn’t fill in the credentials because TWS doesn’t need them – all the information it needs is in the autorestart file. ? For a detailed description of this situation, look at this: . ? So delete that file, and run IBC again: it should be alright. And please don’t use Ctrl-C while TWS is restarting. I recommend you don’t ever use Ctrl-C: it’s not a good way to shut down TWS, if only because you’ll lose any changes you’ve made to TWS’s configuration. ? Richard ? |
IBController suddenly stops working
Been using IBC for months with no issues. Suddenly one day it just stops working. Open the file and TWS loads, then...nothing. Doesn't autofill. Thanks Logs below ? ================================================================================ ================================================================================ ? This log file is located at: ? ? ? C:\IBC\Logs\IBC-3.16.0_TWS-1023_THURSDAY.txt ? ? ================================================================================ ? Starting IBC version 3.16.0 on Thu 11/02/2023 at 21:50:38.92 ? Operating system:? Microsoft Windows Server 2019 Standard? 64-bit? ? ? ? ? 10.0.17763?? ? ? Arguments: ? TWS version = 1023 Program = TWS Entry point = ibcalpha.ibc.IbcTws /TwsPath = C:\Jts /TwsSettingsPath =? /IbcPath = C:\IBC /Config = C:\Users\admin\Documents\IBC\config.ini /Mode =? /JavaPath =? /User = /PW = /FIXUser = /FIXPW = ? ================================= ? Generating the classpath Classpath=C:\Jts\1023\jars\jackson-core-2.12.3.jar;C:\Jts\1023\jars\jts4launch-1023.jar;C:\Jts\1023\jars\jxbrowser-7.29.jar;C:\Jts\1023\jars\jxbrowser-swing-7.29.jar;C:\Jts\1023\jars\jxbrowser-win64-7.29.jar;C:\Jts\1023\jars\locales.jar;C:\Jts\1023\jars\log4j-api-2.17.1.jar;C:\Jts\1023\jars\log4j-core-2.17.1.jar;C:\Jts\1023\jars\total-2020.jar;C:\Jts\1023\jars\twslaunch-1023.jar;C:\Jts\1023\jars\twslaunch-install4j-1.12.jar;C:\Jts\1023\.install4j\i4jruntime.jar;C:\IBC\IBC.jar ? Generating the JAVA VM options Java VM Options= -Xmx768m -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:ParallelGCThreads=20 -XX:ConcGCThreads=5 -XX:InitiatingHeapOccupancyPercent=70 -Dinstaller.uuid=8bcf9c60-dfac-403b-822f-d1cd33b9d908 -DvmOptionsPath=C:\Jts\1023\tws.vmoptions -Dsun.awt.nopixfmt=true -Dsun.java2d.noddraw=true -Dswing.boldMetal=false -Dsun.locale.formatasdefault=true -Dtwslaunch.autoupdate.serviceImpl=com.ib.tws.twslaunch.install4j.Install4jAutoUpdateService -Dchannel=latest -Dexe4j.isInstall4j=true -Dinstall4jType=standalone -DjtsConfigDir=C:\Jts ? Finding autorestart file autorestart file found at C:\Jts\1023\iajkokhhkfokpbefffeopnfbopjjbaikdonojggf\autorestart AUTORESTART_OPTION is -Drestart=iajkokhhkfokpbefffeopnfbopjjbaikdonojggf ? Determining the location of java.exe? Location of java.exe=c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\bin ? Renaming TWS or Gateway .exe file to prevent restart without IBC . ? Starting IBC with this command: "c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\bin\java.exe" -cp? "C:\Jts\1023\jars\jackson-core-2.12.3.jar;C:\Jts\1023\jars\jts4launch-1023.jar;C:\Jts\1023\jars\jxbrowser-7.29.jar;C:\Jts\1023\jars\jxbrowser-swing-7.29.jar;C:\Jts\1023\jars\jxbrowser-win64-7.29.jar;C:\Jts\1023\jars\locales.jar;C:\Jts\1023\jars\log4j-api-2.17.1.jar;C:\Jts\1023\jars\log4j-core-2.17.1.jar;C:\Jts\1023\jars\total-2020.jar;C:\Jts\1023\jars\twslaunch-1023.jar;C:\Jts\1023\jars\twslaunch-install4j-1.12.jar;C:\Jts\1023\.install4j\i4jruntime.jar;C:\IBC\IBC.jar"? -Xmx768m -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:ParallelGCThreads=20 -XX:ConcGCThreads=5 -XX:InitiatingHeapOccupancyPercent=70 -Dinstaller.uuid=8bcf9c60-dfac-403b-822f-d1cd33b9d908 -DvmOptionsPath=C:\Jts\1023\tws.vmoptions -Dsun.awt.nopixfmt=true -Dsun.java2d.noddraw=true -Dswing.boldMetal=false -Dsun.locale.formatasdefault=true -Dtwslaunch.autoupdate.serviceImpl=com.ib.tws.twslaunch.install4j.Install4jAutoUpdateService -Dchannel=latest -Dexe4j.isInstall4j=true -Dinstall4jType=standalone -DjtsConfigDir=C:\Jts -Drestart=iajkokhhkfokpbefffeopnfbopjjbaikdonojggf ibcalpha.ibc.IbcTws "C:\Users\admin\Documents\IBC\config.ini"?? ? IBC Settings: ? ? AcceptBidAskLastSizeDisplayUpdateNotification= ? ? AcceptIncomingConnectionAction=reject ? ? AcceptNonBrokerageAccountWarning=no ? ? AllowBlindTrading=no ? ? AutoLogoffTime= ? ? AutoRestartTime= ? ? BindAddress= ? ? ClosedownAt= ? ? CommandPrompt= ? ? CommandServerPort=0 ? ? ConfirmCryptoCurrencyOrders=manual ? ? ControlFrom= ? ? DismissNSEComplianceNotice=yes ? ? DismissPasswordExpiryWarning=no ? ? ExistingSessionDetectedAction=manual ? ? ExitAfterSecondFactorAuthenticationTimeout=no ? ? FIX=no ? ? FIXLoginId=*** ? ? FIXPassword=*** ? ? IbDir= ? ? IbLoginId=*** ? ? IbPassword=*** ? ? LogStructureScope=known ? ? LogStructureWhen=never ? ? LoginDialogDisplayTimeout=60 ? ? MinimizeMainWindow=no ? ? OverrideTwsApiPort= ? ? ReadOnlyApi= ? ? ReadOnlyLogin=no ? ? ReloginAfterSecondFactorAuthenticationTimeout=yes ? ? SaveTwsSettingsAt= ? ? SecondFactorAuthenticationExitInterval=100000 ? ? SecondFactorAuthenticationTimeout=180 ? ? SecondFactorDevice= ? ? SendMarketDataInLotsForUSstocks= ? ? StoreSettingsOnServer= ? ? SuppressInfoMessages=yes ? ? TradingMode=live End IBC Settings ? 2023-11-02 21:50:39:680 IBC: Version: 3.16.0 System Properties ------------------------------------------------------------ jtsConfigDir = C:\Jts swing.boldMetal = false java.runtime.name = Java(TM) SE Runtime Environment sun.boot.library.path = c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\bin java.vm.version = 25.202-b08 sun.awt.nopixfmt = true vmOptionsPath = C:\Jts\1023\tws.vmoptions java.vm.vendor = Oracle Corporation java.vendor.url = http://java.oracle.com/ path.separator = ; java.vm.name = Java HotSpot(TM) 64-Bit Server VM file.encoding.pkg = sun.io user.country = US user.script =? sun.java.launcher = SUN_STANDARD sun.os.patch.level =? java.vm.specification.name = Java Virtual Machine Specification user.dir = C:\Jts java.runtime.version = 1.8.0_202-b08 java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment java.endorsed.dirs = c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\endorsed os.arch = amd64 java.io.tmpdir = C:\Users\admin\AppData\Local\Temp\2\ line.separator =? ? java.vm.specification.vendor = Oracle Corporation user.variant =? os.name = Windows Server 2016 sun.java2d.noddraw = true sun.jnu.encoding = Cp1252 java.library.path = c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Users\admin\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\DTN\IQFeed;. java.specification.name = Java Platform API Specification java.class.version = 52.0 sun.management.compiler = HotSpot 64-Bit Tiered Compilers exe4j.isInstall4j = true os.version = 10.0 user.home = C:\Users\admin user.timezone = America/Los_Angeles installer.uuid = 8bcf9c60-dfac-403b-822f-d1cd33b9d908 java.awt.printerjob = sun.awt.windows.WPrinterJob file.encoding = Cp1252 java.specification.version = 1.8 java.class.path = C:\Jts\1023\jars\jackson-core-2.12.3.jar;C:\Jts\1023\jars\jts4launch-1023.jar;C:\Jts\1023\jars\jxbrowser-7.29.jar;C:\Jts\1023\jars\jxbrowser-swing-7.29.jar;C:\Jts\1023\jars\jxbrowser-win64-7.29.jar;C:\Jts\1023\jars\locales.jar;C:\Jts\1023\jars\log4j-api-2.17.1.jar;C:\Jts\1023\jars\log4j-core-2.17.1.jar;C:\Jts\1023\jars\total-2020.jar;C:\Jts\1023\jars\twslaunch-1023.jar;C:\Jts\1023\jars\twslaunch-install4j-1.12.jar;C:\Jts\1023\.install4j\i4jruntime.jar;C:\IBC\IBC.jar user.name = admin channel = latest java.vm.specification.version = 1.8 sun.java.command = ibcalpha.ibc.IbcTws C:\Users\admin\Documents\IBC\config.ini java.home = c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64 sun.arch.data.model = 64 user.language = en java.specification.vendor = Oracle Corporation awt.toolkit = sun.awt.windows.WToolkit java.vm.info = mixed mode java.version = 1.8.0_202 java.ext.dirs = c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\ext;C:\Windows\Sun\Java\lib\ext sun.boot.class.path = c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\resources.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\rt.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\sunrsasign.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\jsse.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\jce.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\charsets.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\lib\jfr.jar;c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\classes java.vendor = Oracle Corporation file.separator = \ twslaunch.autoupdate.serviceImpl = com.ib.tws.twslaunch.install4j.Install4jAutoUpdateService java.vendor.url.bug = http://bugreport.sun.com/bugreport/ install4jType = standalone restart = iajkokhhkfokpbefffeopnfbopjjbaikdonojggf sun.io.unicode.encoding = UnicodeLittle sun.cpu.endian = little sun.desktop = windows sun.locale.formatasdefault = true sun.cpu.isalist = amd64 ------------------------------------------------------------ 2023-11-02 21:50:39:680 IBC: Using default settings provider: ini file is C:\Users\admin\Documents\IBC\config.ini 2023-11-02 21:50:39:680 IBC: Using default login manager: getting username and password from args but not found. Will get from settings 2023-11-02 21:50:39:680 IBC: Using default main window manager 2023-11-02 21:50:39:680 IBC: Using default trading mode manager: constructor parameter args but trading mode not present - will be taken from settings 2023-11-02 21:50:39:680 IBC: Using default config dialog manager 2023-11-02 21:50:39:680 IBC: CommandServer is not started because the port is not configured 2023-11-02 21:50:39:820 IBC: TWS Settings directory is: C:\Jts 2023-11-02 21:50:39:836 IBC: Ensuring C:\Jts\jts.ini contains required minimal lines 2023-11-02 21:50:39:836 IBC: Found setting: [Logon]/s3store=true 2023-11-02 21:50:39:836 IBC: Found setting: [Logon]/Locale=en 2023-11-02 21:50:39:836 IBC: Found setting: [Logon]/displayedproxymsg=1 2023-11-02 21:50:39:836 IBC: Found setting: [Logon]/UseSSL=true 2023-11-02 21:50:39:836 IBC: Found setting: [IBGateway]/ApiOnly=true 2023-11-02 21:50:39:836 IBC: Confirmed C:\Jts\jts.ini contains required minimal lines 2023-11-02 21:50:39:836 IBC: Starting TWS 2023-11-02 21:50:39:836 IBC: Re-starting session 2023-11-02 21:50:43:443 IBC: Detected frame entitled: Login; event=Activated 2023-11-02 21:50:43:468 IBC: Detected frame entitled: Login; event=Focused 2023-11-02 21:50:43:468 IBC: Detected frame entitled: Login; event=Opened 2023-11-02 21:50:43:468 IBC: Login dialog WINDOW_OPENED: LoginState is LOGGED_OUT 2023-11-02 21:51:00:575 IBC: Detected frame entitled: Login; event=Lost focus 2023-11-02 21:51:00:575 IBC: Detected frame entitled: Login; event=Deactivated ^C Check for 2FA dialog timed out Check for login dialog display timeout Check for restart call :GetAutoRestartOption Finding autorestart file autorestart file found at C:\Jts\1023\iajkokhhkfokpbefffeopnfbopjjbaikdonojggf\autorestart autorestart file found at C:\Jts\1023\onalcenkffpgmgjdecfipnhfjajfmegaglklfcbo\autorestart AUTORESTART_OPTION is -Drestart=onalcenkffpgmgjdecfipnhfjajfmegaglklfcbo IBC will autorestart shortly ? |
Re: N/A Tooltips
开云体育Very odd. No I’ve never seen one of those. ? Do they just appear for no reason, or is it when you do something or hover over something in particular? ? In any case, it looks like a TWS bug to me, and IBC really isn’t in the business of papering over IB’s bugs. Probably best to report it to them. ? Richard ? ? From: [email protected] <[email protected]> On Behalf Of Jimmy
Sent: Tuesday, October 31, 2023 6:52 PM To: [email protected] Subject: Re: [ibc] N/A Tooltips ? Ah, I thought these tooltips were plaguing?everyone. I don't even know from which TWS windows they come from... maybe charts? ? ? On Tue, Oct 31, 2023 at 2:29?PM Richard L King <rlking@...> wrote:
|
Re: N/A Tooltips
Ah, I thought these tooltips were plaguing?everyone. I don't even know from which TWS windows they come from... maybe charts? On Tue, Oct 31, 2023 at 2:29?PM Richard L King <rlking@...> wrote:
|
Re: N/A Tooltips
开云体育Can you provide some explicit examples? I don’t recall seeing these things. ? ? From: [email protected] <[email protected]> On Behalf Of Jimmy
Sent: Tuesday, October 31, 2023 5:40 PM To: [email protected] Subject: [ibc] N/A Tooltips ? Hi, |
N/A Tooltips
Hi,
I'm sure this is pretty low on the list of priorities in the grand scheme of things, but I notice that we end up with several TWS "Tooltips" windows that only contain the text "N/A". Those are completely useless, and they don't disappear like regular Windows tooltips; they just hang around until one manually closes them. I was wondering if IBC could close these windows automatically as soon as they show up. They offer no useful information, and just clutter up the many windows we have open. Thanks Jimmy |