Bookmap forum

Respectfully bumped

Thanks for your response and for the ideas. The real-time paper trading doesn’t help because the simulator is important for validating ideas without waiting days in the process. Logically these ancient bugs in the existing system should be fixed before new features are added. Please help me. Thanks,...

Bump because Bugs in existing features should be priority. Thank you so much in advance for resolving this quickly. It will make Bookmap so much better. Also, mad props for supporting a Linux build.

:!: Hello this isn’t a feature request but a desperate plea to fix 2 extremely outstanding bugs in the API. After months of talking with support at bookmap.com I’ve been told the way to get a bug solved isn’t through them but by posting a request on the forums. On Thu Apr 25, 2019 3:38 pm I was aski...

For determining if you’re in simulation mode, I recommend adding something in your custom settings for the strategy. I’m adding to this thread because I started it 20 months ago and it’s still not been fixed. Additionally, for an equal length of almost 2 years there has been another bug in the API w...

This is in replay with CQG, but it also happens live with CQG. Here is a link to the 14mb BMF file i'm using,
https://file.io/whFhMc

Do you have an example from v2 of the API for sending/updating an order so it will retain those ClientId labels?

Thanks,
Greg

We're talking about replay mode. Is there another way during replay to poll the system for positions? Also is there a similar method to poll for orders, aside from verifying them as them populate onOrderUpdated?

Bookmap version 7.1.0 build:7 After thorough testing, I have concluded that the PositionListener isn't being called. This can be confirmed by running OrdersDemoNoHistory.java in the DemoStrategies repo here: https://raw.githubusercontent.com/BookmapAPI/DemoStrategies/8980c39106f57926559b6ac74e27b1f1...

Bookmap version 7.1.0 build:7 Sending a parent order, with labels for the ClientId of the attached target and stop-loss orders: SimpleOrderSendParametersBuilder shortOrderSendParameters = new SimpleOrderSendParametersBuilder (alias, false, 1); shortOrderSendParameters.setLimitPrice(bidPrices.get(0))...

Great news, It appears that setStopLossOffset is required, so assuming you want an 8 tick stop loss, the missing line of code was longOrderSendParameters.setStopLossOffset(8); There was not any issue with updating orders. Let me take this moment to say thanks for helping me through it. Thanks, Greg