Mike Medved

Will look into it.

I am not sure whether you're using the historical chart candle values to calculate intraday pivot points? If so, that is not what MT uses. MT uses intraday data to calculate intraday pivot points. So look at intraday high low close - on the intraday chart candles - for the day. Oh and yes TC and BC were reversed. I changed that in code.

Pivot is calculated as (prev day high + prev day low + prev day close) / 3 The difference could be the close of the day. MT takes it from the data, so if you have extended day it will take it from that. Compare your HLC values to MT's.

Time Bars is an indicator that is only relevant for non-time-based charts. It shows the time it took each candle to form.

I have TC = (Prev High + Prev Low)/2 and BC = 2*Pivot - (Prev High + Prev Low)/2 Is that reversed?

Any scan that you can express as references to certain symbol-specific parameters in MT is possible. Simple scans are a set of rules, evaluated one after the other. For example, if the rule is that price percent change change today is between 2 and 100, you can make two rules. 1. if SymbolData.ChangePercent < 2 return and 2. if SymbolData.ChangePercent > 100 return this way if it is between 2 and 100 it will go on to the 3rd rule - see an example rule here: 3rd rule could be - if Volume < 100000 return Note: this way you eliminate all unwanted symbols by doing "and Stop" rules. Then the last rule could be the positive one, for example if Close > 5 Set Color or Set Scan result etc... I thought our videos on scanning or paintbars were pretty clear... But any suggestions on how to make them better are welcome. Of course, if you want to switch the scan to Advanced mode, you would be able to just code the criteria in C#, combining as many of them in one if statement as you want and doing more sophisticated logic.

I'll take suggestions from users on all these points. Not sure what "point 3 is not necessary" means.

1. naming s2-s3 midpoint m0 but r2-r3 midpoint m5 is a bit inconsistent. There should be a logical naming scheme. 2. should each one be selectable or just a general "show mid lines" checkbox? 3. If let's say S1 or S2 are not visible, should the midline between them also be invisible?

'cuz I am not sure what a "floor midpivot" is. Someone else asked for lines that are between pivot lines (like between P and R1 or between R1 and R2) - I am not sure exactly how to do that. Can there be a mid line between P and R2 or only between adjacent lines? Should each one be selectable or just a general "show mid lines" checkbox? What should the label be for the line? If let's say S1 or S2 are not visible, should the midline between them also be invisible?

ehjump - sure. Calc the value in the advanced paintbar code and do a named SetColor and SetYValue for it. Then, in the paintbar, choose the "fill" shape for it and whatever color you like.

Please point me to a link that discusses these.

You’re talking about a “Simple” scan – based on a series of rules. To do what you want you have to have the first few rules rule like this: If Condition then (do nothing) else return negative result and stop And the last rule would be: if Condition then return positive result else return negative result Note the “and stop” in the initial rules – that’s important.

No. MT is written in C# and is a standalone Windows application, does not run in a browser even on Windows, much less on a Mac. Some of our users run MT in Parallels or another Windows emulator on their Macs though.

Oh in case you wonder where the option is (and for those reading this) it is in the Settings. We added a "Search" in settings that allows you to find the setting by just typing a few letters of it in the search.

Ok I checked the code and traced some things and it seems to work as it should. Note: the one-min volume as used in the alert is not what you see in the volume indicator. That volume is divided on 1 min (if that is the frequency) boundaries. The alert machinery just keeps a queue of all ticks in the last 60 seconds. Then it totals the volumes in those ticks and divides it by the number of seconds between the last tick in the queue and the first tick. Then it multiplies that # by 60 to get the running one-minute-volume. That would skew things a bit for very thinly traded stocks... I did it that way so that if you have a sudden uptick in volume in a stock that may not trade every second, the reaction would be faster. Maybe I could just take the total in the last 60 seconds and NOT scale it by the actual time between the last and first tick...