The objection against GET_MAXTICKS is that it is a READ-ONLY field, and so does not allow the end user to experiment with changing this value.
And the plug-in developer knows about this value anyway and would not access it via BrokerCommand(). What would be the use case for this command for the end-user?
Please let's make it also "settable".

Great news for the IB plug-in! I have 2 suggestions:
- for FX/metals let's report *mid-point*- as provided by IB - as Trades. There are no Trades per se for these assets.
- let's also implement IB's *5-sec True RT bars*.
Such 5-sec bar encompasses ALL ticks and comes with a 250-300ms delay - which is good enough for anybody trading at 10-15min+ resolution.
These bars come already cleaned from IB's Historical servers; are exactly equal to the "Historical bars" one can download from IB - and so can be saved to *.t6 structs already in RT (either as 5-sec or as 1min).
250-300ms delay - and you can trade exactly what you would have tested on!

For this to work properly in all cases, Zorro should ideally allow sending a real stop order to the broker (like it already allows with limit orders), not just simulate it.