Mike Medved

You said something about filtering for low volume. What kind of parameter would you like to see for that?

And that's how it should be. If it is not "Reg. Session Values Only" then the after-hour values are included. Or "computed" as the case may be.

Well yes it is on purpose. You want the Close of the Regular Session.

Also - are you sizing your display's DPI to more than 100%?

Have you looked at the Pace indicator and specifically using it in scans? And will look at min volume. Will increase the max.

"Computed" is the way it is done today. You uncheck it, it will use the Prev Close sent in the feed for the last value.

I added the "(For Prev. Close) Always Use Computed Value" option to the indicator. Defaulted to true. Not too happy to have to do it, since this is such a micro-option, but...

All MT can go by is the data it has. As you're showing in the raw data, the trade that MT knows of at 15:59:59 is 27.34. That is what it would show you as the closing price. How can it possibly figure out that the trade at 16:00:06 is the closing price? Note: the timestamps on the trades are (in almost every data provider's case) coming from their servers, not from your computer. So THEY are sending that 19:59:59 timestamp.

I am sorry it took so long, it really is a very simple fix. I will have Jerry give you the latest version on Mon or Sun nite. I changed it to be <16:00:00. But if that is not sufficient probably need to do another quarter of a second or so?

Ok you're saying the value should be at <16:00:00 and not <=16:00:00? Is that the problem?

Ok - but doesn't that already have the "Regular Session Only" parameter? And I love ferrets. Used to have 3.

ydfah, are you using a ferret avatar to soften me up? 'cuz it's working. When you say Previous Close indicator, do you mean the horizontal line with Previous Close selected as the value?

Slope, in mathematics, is dy/dx - where dx is the difference in x between two points and dy is the difference in y. So - if x stays constant, the slope is 0. If the line is vertical (dx=0) then the slope is infinite. (On a coordinate system where X and Y are equivalent, the slope would be the tangent of the angle of the slope). The problem, of course, is - what are the units of dx (dy, I presume, is price). Because obviously the slope itself, unless it is exactly 0, is pretty meaningless if the units of x are arbitrary and unrelated to the units of y (as is the case in stock charts). Thus, the only way you can use slope in stock charts is to compare two of them. To find an approximation of a slope of 20 EMA, or any other function, at point X (let's say X is candle number) is to take its value at X+1, its value at X-1, and divide it by 2 (X+1)-(X-1). The reason it is an approximation and not a real slope is because the chart is not a curve but a set of segments, and the slope at the points where the segments connect is, strictly mathematically, indeterminate. Another way to find a slope would be to fit a Bezier curve or a spline through a set of points surrounding point X, do symbolic differentiation of the curve function, and find its value at point X. Not really feasible. Too complicated. A third way would be to do a linear regression slope calculation on let's say last 5 points and presume that the slope is the slope of the regression line. or, in advanced code in paintbars or scanner (presuming that EMA is the variable representing the value of the indicator) .fctbNone{ color:#000000; } .fctbStyle4{ color:#0000ff; } .fctbStyle3{ color:#000000; } double sumxy = 0; double sumxx = 0; double averagex = 2; double averagey = Average(5,EMA); for (int x=0;x<5;x++) { sumxx += (x-averagex)*(x-averagex); sumxy += (x-averagex)*(EMA[x]-averagey); } var Slope = sumxy/sumxx; Which reminds me - I really should find a way to have the MT looping functions to incorporate the n variable. Right now there is no way to do that, so I had to do the actual loop.

It only resets if the padding was absolute. If padding was %, it doesn't reset. That's on purpose. If padding is 12 for AAPL, it can't stay 12 for KNDI, that would compress the chart to a line.

"Wider Bars" option will be in volume in next beta.

change the up/down volume indicator's colors to brighter ones?

The forum stuff compresses the pic horribly so it doesn't look anything as crisp as the original... But yes, the volume is dimmer. Three reasons: 1. Your selected colors for up/down volume are different from the selected colors for up/down candles. 2. Your candles are set to be outlined, the outline color is bright, so it brightens up the candles in general. 3. The width of the volume bars in MT is set to be a little less than the width of the candles. This is so that adjacent bars don't overwhelm each other. Here is the difference. First is the chart that has the bars the way MT currently does them: Second, same chart, but not making the bar width smaller: The second chart's volume looks sloppy. That's why the adjustment...

Can you press Alt-PrtScr while displaying your chart, then paste in here?

Can you give me a pic showing that? Is the pic below something that shows the problem?

Since the advanced scanner code allows you to look at the value for the indicator N candles back, you can do it that way for any indicator. Including the Single Regression Channel indicator. Let's say you added the Single Regression Channel to the list of variables under the name of SRC. Then the slope would be (SRC-SRC[11])/12

Well... I really didn't want to add another Pivot indicator. So I added TC and BC to Pivot Points. Will be in next beta.

Jason, what I mean is adding the TC and BC option to all pivot indicators, same as they today have R1, S1 etc. Is that a good way of doing this?

As for paintbar drawing a line on the chart - SetYValue sets a point on the chart for each candle, and there is a line drawn through these points.

Well. You know how there is R1, S1, R2, S2.... There could also be TC and BC?

CPR is its own indicator, right?