Page 1 of 1
Fix the damn IB/TWS code...
Posted: Wed May 21, 2025 10:38 am
by hdo
...to reliably generate bracket orders. It works maybe 70% of the time. It also struggles with multiple fills, often only generating partial brackets. I wonder what sort of quality control this adapter has ever seen. Fix it.
Re: Fix the damn IB/TWS code...
Posted: Mon May 26, 2025 12:02 pm
by denysg
Hi Hdo,
Please note that when specifying a bracket order as the order type, you will receive a notification indicating that this feature is implemented on the Bookmap side and may come with certain specifics.
Additionally, it’s worth mentioning that generating partial brackets is expected behavior. The speed of bracket order processing may also depend on the performance of your machine.
Re: Fix the damn IB/TWS code...
Posted: Tue May 27, 2025 3:31 pm
by hdo
Partials are ok as long as they sum up to the entire filled position. But that only happens in about 60% of cases. In 30% it fails to generate any brackets, and in 10% the partials don't sum up.
My machine and connection are top end. Please don't try to play this game. Your software is broken. You know it and you can contact me any time for a live demo of it failing. If you don't care about IB users and can't find resources, at least provide the code of the adapter, so users can fix it themself.
Re: Fix the damn IB/TWS code...
Posted: Thu May 29, 2025 1:20 pm
by nick
Thanks for reaching out and sharing the issue you're experiencing.
For technical matters that may require deeper investigation or troubleshooting, we kindly recommend contacting us directly via our
Live Chat on the
Bookmap website. This way, we can better understand your situation in real time and even initiate a
screensharing session if needed to provide more efficient assistance.
We're here to help and look forward to resolving this for you quickly!
Kind regards,
Nick
Bookmap Support Team
Re: Fix the damn IB/TWS code...
Posted: Thu May 29, 2025 2:37 pm
by hdo
Again, you already have everything. It's your turn to fix the bugs and show a tiny bit of interest in fixing broken software. Surely there is a reason as to why there is no interest, probably I'm the only remaining user of that adapter. That's fine. Then what is preventing you from at least providing the source to users so they can fix the bugs themself?
Re: Fix the damn IB/TWS code...
Posted: Thu Jun 05, 2025 8:18 am
by hdo
Needless to say, it works fine in Quantower, ATAS, and SierraChart. Bookmap seems to be the only company that fails at basic software engineering.
QT and ATAS aren't perfect and have their own bugs and quirks, but not in such critical areas.
If you use Claude Codec with Context7 as MCP pointing to both the Bookmap and TWS API, I'm pretty sure it produces something better than what we have now. I have zero understanding of why you can't just rewrite it.
If IB/TWS support no longer fits your product vision, then communicate that and remove it from the software. Advertising IB/TWS support while letting users lose money due to broken functionality is a huge disservice.