Harmonic Patterns Scanner — Panel FxMath_Harmonic_Hunter_Scanner_Panel(MT5)

The Panel version of the Scanner. Same detection engine and settings as the classic Scanner, but the result table is a scrollable + sortable + filterable panel: mouse-wheel / ▲▼ scrolling, click-to-sort on any data column, and a filter toolbar (Type / Pattern / Time Frame / Acc / Age). Use this when there are more patterns than fit on screen.

#Overview

Unlike the classic Scanner (which draws one edit-box row per signal and can run out of screen space), the Panel version stores every found signal as a row in memory (g_rows[]) and draws only the visible slice inside a scroll window. Filters and sorting operate on the stored results instantly — no re-scan needed — and combine with scrolling.

The scan loop runs from OnTimer() on a minutes-based interval with a g_scanBusy re-entry guard, so the timer and the Scan Market button never overlap — and it works with zero ticks.

#Classic Scanner vs Panel

#The signal table

The table has 13 columns — 11 data columns, a green/red Fltr confirmation mark, and an "Open Chart" action column:

Row cells are named pnl_row<slot>_<col> with fixed slots 0–9, so scrolling and filtering update text in place instead of recreating ~110 edit objects every time.

#Sorting

• Click any column header (pnl_hdr_<col>) to sort by that column.
• Click again to toggle ascending ↔ descending; the active column shows ▲ / ▼.
• Time Frame sorts by minutes (stored as "60", "240"…), so M5 comes before H1 before H4.
• Price / Acc / Age sort numerically; the rest alphabetically (Panel_Less).
• Implementation is a simple insertion sort (Panel_Sort) on the row store — rows are few, so it's instant. Sorting resets the scroll offset to 0.

#Scrolling

• Mouse wheel over the table area scrolls (CHARTEVENT_MOUSE_WHEEL gated by a hover flag set in CHARTEVENT_MOUSE_MOVE).
• Or click the ▲ / ▼ buttons at the right edge of the table (pnl_up / pnl_dn).
• The scroll offset is clamped to the filtered row count (maxOff = nf − PANEL_ROW_VIS), so you can never scroll past the last visible row.
• PANEL_ROW_VIS = 10 rows visible at once, PANEL_ROW_H = 25 px pitch.

#Filter toolbar

The filter bar sits above the table (FILTER_Y = 175) and has five rows:

#Filter logic details

Every row passes through Panel_Matches(r):

• Type: g_fType == "ALL" or row's order type matches.
• Pattern: if any pattern is toggled, the row's base pattern (prefix stripped) must match at least one toggled name.
• Time Frame: if any TF is toggled, the row's TF label (minute string) must match at least one toggled value.
• Acc ≥: acc ≥ g_fAccMin (0 = no minimum).
• Age ≤: age ≤ g_fAgeMax (0 = no maximum).

The row Fltr column is separate from the display filters above. It is a mark, not a filter: each row is evaluated against the enabled confirmation filters (Panel_FilterStatus) using the row's stored symbol/timeframe/D-shift/entry price, and shown green OK if all enabled filters pass, red X if any fails, or gray - if filters are off. Toggling Fltr/Trend/RSI/S/R or editing the HTF field recomputes the marks in place — it does not hide any row.

The Clear button resets: g_fType="ALL", empty pattern/TF sets, AccMin=0, AgeMax=0. Filters are kept across scans (Panel_Reset only clears the sort), so your view persists after an auto-update.

#Timer-driven scanning

This version fixes the classic Scanner's tick-driven behaviour:

• OnTick() does nothing — no header redraw, no scan gating.
• Everything runs from OnTimer(): if Auto_Update and Update_Interval_Minutes > 0 and TimeCurrent() − tTimer ≥ interval, a full run() executes.
• g_scanBusy is set at the start of run() and cleared at the end — the timer and the Scan Market button can never overlap.
• Update_Interval_Minutes = 0 → manual only (no timer armed).
• EventSetTimer is capped at 32767 s; intervals above are clamped.

#Settings (identical to the Scanner)

All inputs are the same as the classic Scanner (47 inputs), with one rename: Uodate_Interval_Minute → Update_Interval_Minutes (correct spelling). The same 14-entry pattern table, accuracy grading, SL/TP modes, trading mode, notifications and .Pouya writing apply. A quick reference:

#View / Open All Charts

• Each row has a View button named view,<idx>,<pair>,<tf> — the index makes rows unique even when the same pair+tf appears with different patterns, and filtered rows open exactly what you see.
• Clicking View opens the chart for that pair at that timeframe and applies the Harmonic_Hunter_Scanner(MT5) template.
• Open All Charts iterates only the currently visible view,* buttons (the filter already removed the rest) and opens each.
• Old View buttons are deleted at the start of each draw (Panel_ClearRows) and recreated for the visible rows — a bug that made buttons disappear on some filter changes was fixed by scoping the cleanup to the view, prefix.

#Panel internals

#FAQ & troubleshooting

Why is a pattern not in the filter list?

Wolfe Waves are disabled (code kept, default false), so they're intentionally not listed. The other 7 families cover all 14 built-in table entries.

My filter buttons did nothing in an old version — is that fixed?

Yes. There were off-by-one bugs parsing the Pattern (pnl_f_pat_ = 10 chars) and Time Frame (pnl_f_tf_ = 9 chars) button names which silently made those two filters no-ops. Fixed in the current code.

The table rows overlap / look wrong after sorting

Rows are drawn into fixed slots 0–9; sorting only changes which stored row index each slot shows. If you see stale text, re-run a scan (Scan Market) — the reset clears the sort and redraws cleanly.

Scans are slow

Trim Pairs / TFs, reduce ZigZag_Window_Bars, or narrow the depth range. The panel redraws only the visible 10 rows, so UI cost is constant regardless of result count.

Does the panel still write the .Pouya file?

Yes — identical to the classic Scanner, so either version can feed the Helper.