PatternSmart.com

MultiCharts .NET: Developing Custom Trading Indicators and Strategies with C#

admin — Sat, 14 Nov 2026 21:56:51 +0000

If you have ever hit the limit of a built-in indicator, you already know the problem. Standard tools are built for everyone, which means they are perfect for no one. MultiCharts .NET indicator development solves that by letting you build exactly what your strategy needs — in C#, with the full power of .NET behind […]

The post MultiCharts .NET: Developing Custom Trading Indicators and Strategies with C# appeared first on PatternSmart.com.

MultiCharts: Converting EasyLanguage Indicators to PowerLanguage – What You Need to Know

admin — Sat, 14 Nov 2026 20:29:05 +0000

If you are moving from TradeStation to MultiCharts, you probably do not want to rebuild years of work from scratch. The good news is that you usually do not have to. When you convert EasyLanguage to PowerLanguage, most classic indicators transfer with little or no change. The risk is assuming that all of them do. […]

The post MultiCharts: Converting EasyLanguage Indicators to PowerLanguage – What You Need to Know appeared first on PatternSmart.com.

MT4: How to Develop Multi-Timeframe Custom Indicators Using MQL4

admin — Fri, 13 Nov 2026 04:43:42 +0000

MetaTrader 4 ships with dozens of built-in indicators, but almost all of them calculate on a single timeframe — the one currently displayed on your chart. A trader who wants an RSI computed on H4 while watching an M15 chart, or a moving average blend of three timeframes at once, quickly hits the platform’s limits. […]

The post MT4: How to Develop Multi-Timeframe Custom Indicators Using MQL4 appeared first on PatternSmart.com.

MT5: Building a Custom Multi-Symbol Market Scanner with MQL5

admin — Fri, 13 Nov 2026 04:10:04 +0000

A MT5 custom market scanner solves a problem every active trader knows well: you can only watch a few charts at once, but opportunity moves across dozens of symbols at the same time. Instead of flipping through EURUSD, GBPUSD, USDJPY, XAUUSD and more, a scanner watches them all for you. It checks the same rules […]

The post MT5: Building a Custom Multi-Symbol Market Scanner with MQL5 appeared first on PatternSmart.com.

NinjaTrader 8: How to Build Custom Market Analyzer Columns Using NinjaScript

admin — Fri, 13 Nov 2026 04:05:03 +0000

Learn how to turn a NinjaScript custom indicator into a NinjaTrader 8 Market Analyzer column, scan futures watchlists, highlight signals, and manage performance. A futures trader may have a dozen contracts on a watchlist, but opening a chart for each one just to check a moving-average condition is slow and repetitive. A NinjaTrader custom Market […]

The post NinjaTrader 8: How to Build Custom Market Analyzer Columns Using NinjaScript appeared first on PatternSmart.com.

cTrader: Custom Indicators vs. cBots – Which One Does Your Trading Idea Need?

admin — Thu, 12 Nov 2026 22:15:30 +0000

If you have a trading idea for cTrader, the first decision is not how to code it. It is what kind of program it should be. Do you need something that helps you see the market more clearly, or something that trades for you when you are not watching? That distinction separates custom cTrader indicator […]

The post cTrader: Custom Indicators vs. cBots – Which One Does Your Trading Idea Need? appeared first on PatternSmart.com.

Trading Indicator Conversion: Why Results Differ Across Platforms

admin — Thu, 12 Nov 2026 22:10:50 +0000

Why Does the Same Trading Indicator Produce Different Results on Different Platforms? You copy an indicator to another charting platform, set the same symbol and period, and expect the same line or signal. Instead, the values drift—or a crossover appears one bar earlier. This is a common problem in trading indicator conversion. The code may […]

The post Trading Indicator Conversion: Why Results Differ Across Platforms appeared first on PatternSmart.com.

How to Turn Your Trading Strategy into a Custom Market Scanner

admin — Thu, 12 Nov 2026 21:15:24 +0000

Most traders already have a strategy. It lives in their heads, in a trading journal, or in a set of screenshots with arrows drawn on them. The problem is not the idea—it is the execution bottleneck. A discretionary setup that requires checking the daily trend, waiting for a pullback, then confirming momentum across multiple charts […]

The post How to Turn Your Trading Strategy into a Custom Market Scanner appeared first on PatternSmart.com.

Non-Repainting Trading Indicators: Understanding Intrabar Signals vs. Confirmed Bar-Close Signals

Patternsmart — Thu, 12 Nov 2026 20:54:49 +0000

Why Traders Look for a Non-Repainting Trading Indicator A non-repainting trading indicator is one whose signals stay exactly where they were printed. Once an arrow, a crossover or a divergence mark appears and the bar closes, it does not move, vanish or get replaced later. Most traders learn why this matters the hard way. A backtest or a chart scroll-back shows clean, well-timed signals. Live, the same indicator flashes a buy, takes it back two minutes later, and prints a different signal one candle to the left. The history looked reliable because the history had been quietly rewritten. Repainting is not always a trick. Often it is a side effect of how indicators calculate on a candle that has not finished yet. Understanding that mechanism lets you judge any indicator, and gives developers a clear way to build signals that hold. This article covers three things: • why an indicator can change while a candle is still forming, • how historical and real-time calculations differ, and why that difference flatters backtests, • how developers implement confirmed, bar-close signals that do not repaint. Why an Indicator Changes During an Unfinished Candle An indicator changes mid-candle because the candle’s own numbers are still moving. At the start of a bar only the open is fixed. The high, low and close update with every tick until the bar ends, so a calculation that reads the “current close” is reading a value that has not been decided yet. Take an oscillator cross as an example. Mid-candle, price spikes and the oscillator crosses its trigger level, so an arrow prints. Before the bar closes, price falls back, the oscillator drops under the level, and the arrow disappears. The closed chart never contains that arrow. The trader saw it live, but the history never recorded it. one candle at three moments · arrow appears, then disappears The dashed line is the signal level. The same candle crosses it mid-bar, then closes below it, taking the arrow with it. The long upper wick is all that remains. The usual suspects are any rules that depend on the live bar: moving-average crossovers, oscillator level crosses, band and channel breakouts, and anything that uses the current bar’s high or low. These rules lead to two kinds of signal: • Intrabar signal: calculated on the forming candle and refreshed on every tick. It arrives early, and it can flip or vanish. • Confirmed (bar-close) signal: calculated once the candle has closed, from its final open, high, low and close. It arrives later, and it stays. Neither is wrong. They answer different questions, and the trade-off between them comes back later in this article. How Historical and Real-Time Calculations Differ Trading platforms treat a chart’s past and its present differently, and that gap is where many “perfect” backtests come from. On historical bars, every candle already has its final open, high, low and close. The platform runs the indicator once per bar on those final values and keeps the result. In real time, the newest bar is still open, so the indicator runs again on each price update using provisional values. history vs live bar · one pass per bar vs recalculation on every tick Two consequences follow: 1. History shows only the survivors. Live, you watch every flip. In the stored history, only each bar’s final outcome remains. A signal that appeared and vanished three times live shows up as one clean entry, or nothing at all. 2. Backtests can know too much. A rule that reads future or unfinished data on historical bars gets the final answer for free. A higher-timeframe value is the classic case. On a 15-minute chart, the daily close is only known at the end of the day, yet on history the platform can hand it to every 15-minute bar of that day. This is called lookahead, and the backtest ends up trading on information that did not exist yet. The platforms behave like this in their own ways: • MetaTrader 4: the indicator is called on every tick. The first call computes the full history, and later calls update only the newest bars. Code that rewrites bar 0, the forming bar, on each tick is the most common cause of repainting there. • TradingView Pine Script: the script runs once for each historical bar, then re-executes on every update of the live bar, rolling its variables back before each pass. The built-in barstate.isconfirmed is true only on the final execution of a bar. Four Kinds of Repainting, and One Look-Alike Repainting is not a single bug. Four different mechanisms produce it, and they call for different fixes. Type What the trader sees Usual cause Fix Intrabar repaint A signal appears and disappears on the forming candle Rules read the live close, high or low Evaluate on the closed bar Lookahead repaint History is cleaner than live trading Higher-timeframe or future data read on past bars Use only completed higher-timeframe bars Pivot or zigzag repaint Swing marks move or are redrawn as new bars arrive A swing is only certain after bars to its right Signal on the confirmation bar Recalculation repaint Old signals change after a reload or a data refresh Logic depends on the visible range, bars loaded or revised feed data Make each bar’s result independent of the others The look-alike is a delayed signal. A swing-high marker that appears five bars after the high, and then stays put, is late but honest. It does not repaint. What repaints is the version that draws the marker back at the high itself, so the chart looks as if the indicator had called the top in advance. This difference matters when you compare tools. A delayed, confirmed signal is less exciting on a chart and more trustworthy in a trading account. How Developers Implement Confirmed Bar-Close Signals The core rule is simple: a signal may only be decided from data that can no longer change. Everything else follows from it. bar-close signal flow · 1 decision, 1 loop Until the close, the indicator waits and draws nothing. Five habits keep it that way: […]

The post Non-Repainting Trading Indicators: Understanding Intrabar Signals vs. Confirmed Bar-Close Signals appeared first on PatternSmart.com.