Mike Medved

Hit the Ins key and type several symbols separated by commas or spaces.

When you are drawing a line on an MT chart, on the horizontal and vertical axis it shows you the line measurements. As for triggering a trade - no, MT doesn't auto-trade. There are a lot of reasons for it. It is not as simple as just triggering a trade.

It's not really hidden - the paintbar is painted under it... you could change the color of either text or the paintbar, and it would show better. The problem with doing micro-customizations like that is that the options just multiply out of control and no one knows about them. What you can also do is make an "empty" paintbar - one that never has colors. Then place it on the chart showing as band on bottom before the other paintbar. Adjust its width to match the height of the text. That will push the next paintbar higher.

Well... The whole point of the heatmap is to have things subdivided by sector and by size and nicely tiled etc. etc. I don't see how to do it with an arbitrary collection of stocks, when you don't know to which sector each belongs.

Currently - no cannot thicken it. Will see.

The trades are recorded in pressure bars only if they go at (or, depending on the setting) below bid or at or above ask. NOTE that the "bid" and "ask" in the previous sentence are not the current tick's bid or ask but the previous tick's bid or ask. If the trade went off between bid and ask, it would not be recorded.

Contact us at support@medvedtrader.com, suggest your favorite payment method, and we will individually process it.

Again - does "timeframe" mean different candle frequencies. Like a scan for 1-minute candles and 30-min candles? If so, no, you cannot do that on one portfolio. What you can do though is make a copy of the portfolio, open that in a different window, with the same data source (that way the same data source will feed both portfolios) and apply the scan to the second portfolio for a different candle frequency.

This has to be done with an Advanced paintbar. I will post the code of it here, and also attach the .pbexport file. Take the file, save it somewhere, go to the Scan/Paintbar Manager and import it. 1. Define SMAHigh to be an SMA of period 8 based on High. 2. Defne SMALow to be an SMA of period 8 based on Low. 3. Code of paintbar: .fctbNone{ color:#000000; } .fctbStyle5{ color:#0000ff; } .fctbStyle6{ color:#808080; } .fctbStyle2{ color:#008000; } .fctbStyle4{ color:#000000;font-weight:bold;text-decoration:underline; }public void MainCalculation() { SetColor(Color.Yellow); if (Close>SMAHigh) { SetYValue(SMALow); CurrentState.DisplayingLow = true; } else if (Close<SMALow) { SetYValue(SMAHigh); CurrentState.DisplayingLow = false; } else if (CurrentState.DisplayingLow) SetYValue(SMALow); else SetYValue(SMAHigh); } /// <summary> /// Is called at start of paintbar calculation, should be used to initialize anything needed for the paintbar /// </summary> private void PaintbarInitialize(){} /// <summary> /// Holds paintbar state - fill with variables needed to be preserved for next paintbar calc /// </summary> private struct PaintbarState { public Boolean DisplayingLow; } /// <summary> /// Holds current PB state - use to calc PB, changes to it carry over to next PB calc /// </summary> private PaintbarState CurrentState; /// <summary> /// Holds saved PB state - internal /// </summary> private PaintbarState SavedState; /// <summary> /// Is called at start of paintbar calculation, should be used to clear the paintbar state /// </summary> private void PaintbarClearState() { CurrentState = new PaintbarState(); } /// <summary> /// Saves paintbar state (called internally). /// </summary> private void PaintbarSaveState() { SavedState = CurrentState; } /// <summary> /// Restores paintbar state (called internally). /// </summary> private void PaintbarRestoreState() { CurrentState = SavedState; } highlowsma.PBExport

There are some indicators that are good for checking volatility - such as ATR and Bollinger Band Width, Choppiness Index or RVI. So you can use those - comparing the value of the indicator N candles back vs right now. As for your second question, what do you mean by "different timeframe"? Candle frequency?

Thank you. That bug has been there forever, I think. Fixed in the next beta it will be, young padawan.

The new StochRSI that will allow selecting MA type and adds a smoothing period will be in next beta.

There is also "Pace" indicator. It is a pretty good measure of how abnormal the volume of trading is and is flexible in its parameters.

I don't see any place for the missing "smoothing" period value in the calculation I have. Lemme give it to you - point out what is not correct. 1. Diff = Close-Prev Close 2. AveUp = MA of positive Diffs for the last "Period" candles AveDown = MA of negative Diffs for the last period candles (absolute value of it) 3. RS = AveUp/AveDown 4. RSI = 100 * RS / (1 + RS) - or 100 - (100 / 1 + RS) if you prefer 5. HH and LL are the highest and lowest values of RSI over the last "St. Period" values 6. Main = 100*(RSI-LL)/(HH-LL) 7. Signal = MA of "Signal" period of Main 8. Plot Main and Signal I think what you are saying is that another MA is applied to the result of step 6 before step 7. But I don't see it anywhere I googled for StochRSI algorithms. Another interesting twist I saw in some StochRSI definitions is that the HH and LL are calculated without taking into account the latest RSI value. I could do that as well but would have to know for sure that that is the correct way of doing it.

Ok, comparing what you showed to MT's code: 1. to calculate actual RSI - MT uses either EMA or Wilder's EMA depending on the setting. Are you saying that SMA should be included? 2. To calculate %d (signal) - MT uses EMA. Are you saying that it should use SMA, or have an option of EMA/SMA? Or all three? Should that setting be shared with (1) above as well?