Greetings everyone,
This is Joshua over at Opentick. Just thought I would join in on this thread and offer some information. I began using the Multicharts Beta build about 3 or 4 weeks ago, that initially had Opentick support.
Any attempt I have made in creating custom exchange codes has caused strange problems. In trying to troubleshoot one users issues, I created the "EM" exchange code, and set up a symbol in the quotemanager to use it. The quotemanager eventually notes that it is recieving ticks, and after leaving it unattended for a few hours it gathered up a nice amount. However, when attempting to load a chart (real-time otfeed data, and local data-cache), none of this data gets drawn on the chart, and no new real-time ticks do either. The same result has occured for me every time. They remain in some kind of "sorry, no data" state. I think at one point, the price in the title bar for the Chart was updating with data, but nothing was ever drawn in the chart. Actually, "editing" the data didn't work either. The dataset appeared to be empty.
I noted a number of other issues is some recent emails to Kate; I figured she would have forwarded these onto the team. In most cases I have told our users to wait for the next build of Multicharts, as the current build's support for otFeed is immature as of yet, and does not include exchange codes (yeah, we can create them ourselves - but this didn't work for me. and since the ones I do create manually do recieve data, but don't get drawn in a chart....?). I see now that there is a more updated build available than what I was using in my attempts, so maybe that resolves the issues I was having; but I didn't see much noted about OT in your changelog.
For the case of using Nasdaq though (The "NASDAQ" exchange code), which our system does support, and was an exchange code that existed in Multicharts, I had no problem recieving data and having it charted. Left it running for a couple weeks actually. I primarily used the real-time data source and local data-cache kind of charts though. This is how I initially tested otFeed under MultiCharts and it worked well.
MultiCharts is a great product - probably my favorite charting platform that I've used recently. Really, we are prepared to offer whatever developmental resources are necessary to ensure the satisfaction of our mutual users. If your dev team wants to work with ours a little more closely in debugging some things. IE: we can watch server side and help troubleshoot strange issues, for example. Whatever we can do to help!
Yeah, our historical database has it's kinks - I'll be the first to admit it, so maybe it's worth it to note that functionality will probably be better using otFeed as a real-time data source, until our historical database has matured more - and believe me it is maturing fast
![Smile :)](./images/smilies/icon_smile.gif)