Hi, guys.
Every simple interaction with WL takes much more and more time...
Just now I tried to edit IB extension settings and ran into odd behavior. Feeling myself like a QA.
1. Data Provider specific settings works correct only first time.
If I delete the "Settings" file in the user data directory, I could make some changes and them would be saved. But if I reopen Data Manager and try to make changes again – neither would be saved.
By this behavior are affected all fields.
2. IP addresses other than 127.0.0.x are not supported.
If I enter, for example, 192.168.88.21 – it would be dropped during saving and keep just "1" in this field.
Within neighbour IQFeed extension everything works fine (IP, username/password changes).
And one other proposal:
- It would be great if hostname could be specified as a Data Provider host, and not only IP addresses.
Every simple interaction with WL takes much more and more time...
Just now I tried to edit IB extension settings and ran into odd behavior. Feeling myself like a QA.
1. Data Provider specific settings works correct only first time.
If I delete the "Settings" file in the user data directory, I could make some changes and them would be saved. But if I reopen Data Manager and try to make changes again – neither would be saved.
By this behavior are affected all fields.
2. IP addresses other than 127.0.0.x are not supported.
If I enter, for example, 192.168.88.21 – it would be dropped during saving and keep just "1" in this field.
Within neighbour IQFeed extension everything works fine (IP, username/password changes).
And one other proposal:
- It would be great if hostname could be specified as a Data Provider host, and not only IP addresses.
Rename
Amazing! If I paste an IP address from clipboard at first run after deletion of settings file – it saves correctly! But all other fields still doesn't save any changes.
Same thing on second PC.
Thanks for the report. I corrected the issue with the setting changes not sticking. We recently made some changes in that area, apologies for the failure.
One another potentially interesting moment.
If I set correct settings (by using Settings file workarounds) to the IB provider, I get following error:
I queried API on the same machine and with the same IP/port setting with my custom tool and it worked without issues. Hence I conclude that something is wrong with the WL.
If I set correct settings (by using Settings file workarounds) to the IB provider, I get following error:
I queried API on the same machine and with the same IP/port setting with my custom tool and it worked without issues. Hence I conclude that something is wrong with the WL.
Maybe we can schedule a Zoom support call to see if we can't help? If interested, write us at support@wealth-lab.com.
You're connecting from a different machine that doesn't have TWS installed? That going to be a problem right now.
It would help to know exactly what your setup is. PC and/or Mac, where is TWS installed, on which machine is it running?
A few builds ago we made it easy to detect, auto launch and connect to TWS on the same machine, but that came at an expense to connecting from other machines.
It would help to know exactly what your setup is. PC and/or Mac, where is TWS installed, on which machine is it running?
A few builds ago we made it easy to detect, auto launch and connect to TWS on the same machine, but that came at an expense to connecting from other machines.
I have two Windows machines. First of them have IB gateway and I'm trying to connect to it from the second machine, that haven't TWS/IB gw installed.
At least for now, you should install and run IB Gateway on the same machine with WL7. If you want to use the Gateway and not TWS, then it needs to be running before WL7 tries to connect.
Down the road we can probably attempt a non-local connection to a running IB Gateway/TWS before entering the current logic, which first looks to see if either process is running on the local machine. If it doesn't find the process in memory, it attempts to launch TWS from the c:\jts folder.
Down the road we can probably attempt a non-local connection to a running IB Gateway/TWS before entering the current logic, which first looks to see if either process is running on the local machine. If it doesn't find the process in memory, it attempts to launch TWS from the c:\jts folder.
QUOTE:You can enter a name if you like - we pass it straight to IB's eConnect method, so it's up to IB's API and/or the OS if that works or not.
It would be great if hostname could be specified as a Data Provider host, and not only IP addresses.
QUOTE:
At least for now, you should install and run IB Gateway on the same machine with WL7. If you want to use the Gateway and not TWS, then it needs to be running before WL7 tries to connect.
Oh, very interesting. But it works. I just ran TWS and minimized it without login and now WL communicates with IB gateway on other machine without any problem. Non-obvious thing.
QUOTE:
Down the road we can probably attempt a non-local connection to a running IB Gateway/TWS before entering the current logic, which first looks to see if either process is running on the local machine. If it doesn't find the process in memory, it attempts to launch TWS from the c:\jts folder.
I think, there is a simpler way – add a checkbox in the settings, with name like a "Launch TWS at connect" and that be checked by default (for better regular user experience). Such solution is used in the Multicharts, for example.
QUOTE:
You can enter a name if you like - we pass it straight to IB's eConnect method, so it's up to IB's API and/or the OS if that works or not.
Yes, it worked, thank you. Seems that field name confused me.
I'm glad the non-local connect worked for you, but frankly I don't know how it could work in Build 16 or 17...
... Now that I think about it, the auto-reconnect logic probably made that work. Nonetheless, Build 18 will attempt a "blind connect" before checking local processes and/or launching TWS locally.
... Now that I think about it, the auto-reconnect logic probably made that work. Nonetheless, Build 18 will attempt a "blind connect" before checking local processes and/or launching TWS locally.
QUOTE:WL7/IB Provider already auto launches TWS whenever any data or broker connection is required. You don't even have to check a box.
I think, there is a simpler way – add a checkbox in the settings, with name like a "Launch TWS at connect"
QUOTE:
WL7/IB Provider already auto launches TWS whenever any data or broker connection is required. You don't even have to check a box.
I meant was that I could uncheck the box to avoid running local TWS in case of using a remote gateway. But ok, "blind connect" also resolves this issue.
Your Response
Post
Edit Post
Login is required