开云体育

You can have the main TWS window minimized by using this setting in config.ini: MinimizeMainWindow=yes I can’t guarantee that this will work consistently on macOS as I don’t have access to

Haha yup that worked sorry about that. I appreciate what you guys are doing with this. It makes life easier when working with an already annoying user experience with IBKR. While I have you, is there

Read the notes for the TWS_MAJOR_VRSN variable in twsstartmacos.sh. It says this: # TWS_MAJOR_VRSN # # Specifies the major version number of TWS to be run. If you are # unsure of

I'm trying to set up IBC 3.18.0 on my macOS with TWS version 1019. Attached is what my directories looks like. I installed the offline version of TWS 10.19 for macOS but it's still saying I don't and

Mark Perhaps you didn’t see, or didn’t read properly, my post on 10 September? If not, please read it! Then, please, can you respond to what I asked? Which was this: Have you actually

That’s irrelevant now. I’ve understood the difference. I need you to respond to my post from yesterday. Sent: Monday, September 11, 2023 4:33 AM To: [email protected] Subject: Re:

Mark I don’t think this is going to work. I’ve done the changes I suggested, and when IBC runs it sets the right things in jts.ini, which ends up like this: [IBGateway] ApiOnly=true

Mark Ok, I’ve spent some time looking at this, and I think I know what I’m going to do. What I propose is to introduce a new setting in config.ini, which will be like this:

At the moment, the answer is ‘no’: there’s no way to disable SSL with IBC. However, it should be possible to amend IBC to allow this. I’m out for the day, so I can’t look at this

Can you please explain what you’re trying to do, because I have no idea what you’re talking about. What do you mean by ‘cross connected logins’? TWS no longer allows not to use SSL. If you

Did some digging during the weekend and found out that code 137 is related to running out of memory. After checking the memory consumption and noticing it running at 100% I think we can close this one

No idea. Exit code 137 means that the process has been sent a KILL signal. Nothing in IBC ever does this, so there must be some external reason for it (for example, running out of memory would do

Hi! I have started to get this error message after a couple of hours up time: /root/ibc/scripts/ibcstart.sh: line 504:? ? 28 Killed? ? ? ? ? ? ? ? ? "$java_path/java" -cp "$ibc_classpath"

Hi Richard, Unfortunately, I do not have any of the previous logs.? I am 95% sure that the situation that you described above is not what preceded the issue.? However, if it happens again I shall

Alistair The way to avoid this is not to do something that causes it to happen! I realise that’s a bit vague, but actually it’s quite difficult to make this happen at all. I’d be

Hi Richard, After posting this, I kept searching and found this thread: /g/ibcalpha/topic/97467926#2020.? Following the steps there has solved the issue. How best to avoid this in

Hi Richard, IBC Gateway had been working until this morning.? However, now it does not populate the username and password fields and log in.? It was a problem that I encountered when using Gateway

Hi Richard, Yes now everything is clear. Thank you very much for you patience. Federico

Federico For precision, I’ll comment on each individual sentence of your reply. Note that references to TWS also apply to Gateway. So basically I should for example have a scheduled task

Hi, Thanks for the reply. So basically I should for example have a scheduled task that runs every day of the week the StartTWS.bat in the morning (I guess for the time limit of 23 hours on the