Please check overlay for errors

—  I have a 60 min chart with symbol $SPX I have an overlay of /ESM2 

1 comment | category: InDevelopment | Views: 0

Multi-Terminal

— MetaTrader offers a Multi-Terminal for MT4 allowing simultaneous control of multiple acounts.  This is a very useful feature offered by many other Brokers.  I am very satisfied with MBT but need to manage multiple accounts.  I've spoken with a couple people at MBT and have only been told they had not heard of it but would check into it and call back...no word yet.  Can someone please take a serious look at this feature and let me know if it is something MBT can implement?  read more...

1 comment | category: General | Views: 3

Options

—  Probably the singlemost biggest request that I have with MB is to make options on futures available .
 
 I love trading with MB but I hate having to go to another broker for these .

 Options on futures are a great way to hedge currency risk also as well as provide an alternative for people that want to trade other futures contracts without having to put up a large amount of margin .
read more...

1 comment | category: General | Views: 10

percentage change button

—  Please add a "percentage change from open" for all the day traders. Thanks. read more...

1 comment | category: MBTDesktopPro | Views: 7

Quote server lockout after too many requests: Needs improvement

— MBT has recently imposed a limit on the rate of requests made to the quote server. This new policy imposes an unnecessary burden on SDK users who attempt to download historical data.

As explained by Phil Huether in response to my inquiry, this was implemented because some SDK users were sending frequent and repetitive server requests for the current tick/minute/day bars rather than performing a single request with "bUpdate = true" which would provide automatic periodic updates.

MBT's current solution is to create a lockout period (it appears to be one minute) if a user exceeds a certain rate of quote server requests (which appears to be about 40 requests within one minute). During the lockout period all subsequent requests are responded to with a errClientSideConnect. Furthermore, any request made during the lockout period adds to the tally of requests and therefore may extend the lockout period.

As MBT did not provide any notification or explanation of this new policy, I have determined the above empirically and may not have all the details exactly right.

Unfortunately, this lockout policy has the side-effect of hindering the legitimate download of historical data. When I tried to download 6 days worth of historical tick data for AAPL (using the maximum supported chunk size of 25K records per request), I hit the 40 request trigger after receiving only a few days of data.

To properly handle the situation, it is necessary for SDK users to do implement something like the following:

• Maintain a back-up copy of the parameters of every request in case the dreaded error occurs.
• Upon getting the error: halt further requests and wait some period of time (which seems to be 1 minute).
• Re-send any failed requests.
  

1. Rather than aborting all requests for a lockout duration, simply throttle responses to new requests when a user's requests become excessive. This would be transparent to the user (aside from the reduced performance) and wouldn't require users to write special error handling code. Simply delaying the response by one minute rather than aborting the request would be a big improvement.
2. Since the goal is to discourage users from making continuous requests for realtime data rath

add a comment | category: Implemented | Views: 22

Where is BlackBerry platform?

— I remember there is application for BB not long ago, where can I find it? 

add a comment | category: NoImplementation | Views: 5

Line Drawing Issues

— I regularly run into problems with displaying and copying lines.  If I try to copy an angled line that does not have the two little boxes that originally defined the line displayed on the current viewed area of the chart, then the resultant line will be vertical off the edge of the displayed area.  Also, if I try to move the original line where the two boxes are not visible on the current view, the line jumps to some goofy angle sometimes off the displayed view and its original version is now gone.  Also, I am starting to notice that some of these lines disappear without explaination on some time intervals.

An example of the first problem is a continuous angled line drawn from a point 10 days ago to a point 2 days ago.  Now switch to a shorter time frame that only show the last couple of hours (use a line that was drawn such that it should be visible currently) and then try to copy or move it.  I have also noticed that angled lines occasionally get tweeked out of their original alignment slightly, but I haven't quite figured out how to predict when it happens, and I do not rule out some operator error on my part.

MT4 doesn't seem to have any of the problems above, but it would sure be nice to be able to rely on the lines drawn on Desktop Pro rather than having to use both packages.  I realize this probably does not impact a lot of people, but it is a problem.
read more...

2 comments | category: Implemented | Views: 2

Market Depth window

— I like to see information displayed left to right in the order of least to greatest. I wish the Market Depth window would show the Low Price of the day on the left and the High Price of the day on the right. Then I could glance at it and intuitively see the spread for the day - lowest to highest. I also wish that Previous Close price and Open price could be on the same line - in the order Previous Close then Open. This way I could glance and see the movement from yesterday to today. This way you could move Last Tick and Last Vol to the same line. read more...

3 comments | category: NoImplementation | Views: 7