Mike Medved

Gimme a screenshot of TWS style?

Was a bug in one of the routines that attempt to detect erroneous data. Fixed in next release.

carlisle - I just sit here in the corner and code. MTG is the guy who has some expertise in this, I am sure he can throw in a couple of links.

For people other than MTG that are looking at this thread - next release will include "3-touch trendlines" as an indicator. Feel free to try out and comment.

MTG, I tried playing with this stuff... 1. I think one of the parameters needs to be "minimum distance between touch points" - in candles/bars, because very often it creates a trendline on points that are very close to each other. 2. It really does not find many (almost none) 3-point lines on any charts I tried, unless you increase the "error" range on the third point quite a bit. 3. I presume if the chart goes through the 2-point line at some point, before it becomes a 3-point line, that kills the 2-point line, right? 4. Can you give me an example historical chart that has a 3-point line like that so I can test my code on that stock's data?

Don't worry about pointiness We're after suggestions however pointed. Anyway - I do like your suggestion. I gotta think about how to implement that efficiently... Question: when you say give a tolerance on 3rd point, does it have to be the middle one of the 3?

When you say "2 touches can be drawn between any two points on the chart" you really don't mean that, right? You mean between any two local minima or maxima. Same with the third touch - it has to be the local minimum or maximum. That's what the "strength" parameter is for the current auto-trendlines - it is the # of candles that define a local minimum or maximum.

Yes. Once we allow custom indicators. We need to provide the editor for it, with syntax detection, compile errors etc etc etc. Then deal with the security issues. But we're working on this. The ticks will be available to you in the custom indicator to compute whatever you want... Still - computing an indicator on every tick (instead of on the candle's values) during a "full recalc" on initialization of the chart will be slow, so I would suggest doing that only on the partial recalcs (that is, as the data comes in). I will address this in the manual when we release the custom indicators.

It's an interesting idea but I would put it on the back burner for now. We are in the middle of an effort to try to finalize MT, create the web site, the help file, the backend etc, and push it out. After that, we will continue normal development.

I am currently in the process of building MT web site. One of the pages will be a Screenshot Gallery Please email us (to support[at]medvedtrader.com) your favorite screenshots that you think highlight well various MT's features. Can be multi-window or one-window screenshots. If you have a multi-monitor workstation set up that runs MT, take that picture too (make sure all the Coke cans are off the table ) Please blur out all personal details from the screens - I will also look out for them and blur them out before placing the pics on the web site. If you like, include a text blurb (not too long) that describes what's in the screenshot - to be included in the gallery. Thanks Mike

I discussed it with Jerry - I have the basic doc ready, unfortunately there are some issues that we have to resolve, as well as UI for it. It's not forgotten.

MT does write to disk quite a bit. It uses memory-mapped files, so changes it makes (as data comes in) get flushed to disk. Antivirus programs monitor disk writes and will slow things down.

zenlando, in QT, if you have two inline charts on the same symbol, they cannot have different "extended hours" setting. If you set it to never show extended hours on one, it will set it to the same on the other one. In MT, you can set it to be different on two different charts for the same symbol. That is why you cannot do one trendline alert that would show up on both charts. BUT. We are making it so that if you have two intraday charts that are time-based and have the same time frame and extended hours setting (but different frequencies, for example), they will share the trendline alert. Once done, it will be in next release.

Trendline Alert being unique to chart: imagine a trendline drawn on a chart that never shows extended hours, with both anchors set one day back. Then think of the same line, with same anchors, drawn on a chart that shows extended hours for the last day. The position of the continuation of the trendline on current day would be different between the two charts. So you cannot do a trendline alert that is not unique per chart - it would be ambiguous.

By this, do you mean take the last year's yields from historical data, add them up and show that as percentage of the "paid" price?

Once I finish the documentation of how to write indicators (working on it now) you will be able to do this and almost anything else you can think of.

In MT, click on Fib Fan on the Draw Tab, then draw it on the chart.

I have to sit down and spend a few days writing a doc about how to write indicators in MT... It's a big project Will do that some time in the next couple of months.

Mid point - the bar in which there is the volume where volume above and volume below are equal POC - biggest volume bar

Hm... We could, for all indicators, add the "fixed range high/low" parameter that would allow you to set fixed range for currently dynamic indicators or change the fixed range for currently fixed ones... The only problem is complexity. This adds more "stuff" to that window. Users get scared when faced with so many choices.

The way we utilize SDATA.BIN file, unless you call up a lot of charts that have a lot of data, they do not eat up memory or slow things down. That is, data that is not being used (like showing it in a chart) just sits on disk, and doesn't figure into anything. So SDATA.BIN file can grow arbitrarily large and the only thing it will affect is when you export it or back it up...

Can you give me links to such indicators somewhere out there?

Ok thanks. That bug is now fixed and you will see the fix in next release. Here's the logic MT uses: 1. For the same indicator (that is, if you link two or more of same indicator with diff parameters), the axis is reused 2. For others, it looks at ranges. If one range is less than 4 times the other range, same axis is used. Otherwise, it splits off another axis. 3. 3 maximum axes' values are plotted. The other axes would still work but their values would not be shown. What you're seeing (some dynamic, some fixed) is just how each indicator is programmed. Some indicators have fixed ranges - like 0 to 100, always. Some are left to be dynamic.

will go look at that. On edit: looked and fixed it. Same indicators should always share an axis now. Will be in next release.

Hmm Can you give me an example of two indicators that, when linked, will show values on one axis and not spread it on two? That definitely needs to be fixed.