Bookmap forum

Average position price is shown as a thin line on the price axis.

> I seem to recall other indicators are able to repopulate without reloading the indicator. I don't think this relates to core API. Simplified API - yes, but it sacrifices efficiency for simplicity. When tab is opened (or reopened) you get a call to ScreenSpacePainterFactory#createScreenSpacePainter...

If I'm not mistaken, when tab is switched old ScreenSpacePainter gets disposed (you get a callback and must destroy relevant canvases) and then you will get a request to create a new one when user switches back. Do you handle disposing the old one/creating new one?

You are still using simplified API. We have confirmed that what you are experiencing is bookmap bug and will fix it, hopefully soon.

Hi. Start with inspecting the logs that were produced first time you tried loading this jar file. There are no known caching issues, typically you'll find something like classes being compiled with wrong version of Java (above java 14 for 7.2).

Not via UI, but if you open "C:\Bookmap\Config\launcher-options.conf" on Windows you can edit xmx parameter there

Hi. At this point GPU usually does not matter much. It just has to be "good enough", but going overboard usually does not help. In this case it seems that crypto providers that you use just provide overly detailed data - since the minimal transaction size is usually quite small and price granularity...

Is your indicator using core API or simplified? Which version of bookmap are you using?

I'm sorry, but I failed to reproduce that quickly. This is the code I used to test it:  LastTradeDemoNoHistoryUsingPips.java and it loaded fine with live Rithmic when I restarting bookmap with "load workspace" checkbox on the launchpad. Could you please provide more details? Ideally - a code sample ...

initialize is not guaranteed to be started from EDT. You should use SwingUtilites.invokeLater in order to do any UI work there.

https://docs.oracle.com/javase/tutorial ... patch.html