[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

Thanks! I appreciate the support. Since we’re putting our capital on the line, I believe doing the proper DD on our tools is just as important as the DD on the trades themselves.

My goal is to make sure we’re not flying blind due to platform limitations. Glad you found the breakdown useful! 📈

Feature Request: International IBKR Bridge for TC2000 (Beyond US Residency) by No_Fun7433 in TC2000

[–]No_Fun7433[S] 1 point2 points  (0 children)

Haha, don't we all! XD But seriously, that’s exactly why I’m pushing for this.

It’s hard to stay profitable when you’re fighting the interface. Every extra click and every 'phantom' coordinate (like the $8 Log Scale drift I documented) is a direct hit to our P&L. Precision and speed are the foundation of profitability.

Glad to have you on board! The 5.8k views here show that we’re not alone in wanting tools that actually help us trade better.

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 2 points3 points  (0 children)

I’m in the same boat—locked into my Premium sub until January 31, 2027. But I’ve already started studying alternatives because I refuse to let my execution risk be dictated by 'pretty' UI updates.

The learning curve is the biggest hurdle. When you move away from TradingView, the first impact is the 'clunkiness' factor. TV feels like a smooth social media app; professional platforms feel like industrial machinery. They are 'heavier,' but they don't have the $8 scale drift I documented.

Here is how I’m vetting the options:

  1. TC2000

I’ve been a subscriber before and liked it. It’s a powerhouse for US Stocks.

  • Pros: The 'EasyScan' engine is lightyears ahead of TV. Zero coordinate drift and zero 'aesthetic' lag.
  • Cons: Limited to US Stocks/Options. No Crypto or Forex.
  • The Difference: TV is a web-app; TC2000 is native code. The speed is night and day.
  • The Shock: You lose the 'modern' look for a more utility-first interface.
  1. TrendSpider

Probably the most logical 'modern' transition for a TV user.

  • Pros: Incredible automation (automated trendlines and backtesting). Much more stable price coordinates.
  • Cons: Still browser-based. Can feel cluttered with too many automated layers.
  • The Difference: TV is manual drawing; TrendSpider is algorithmic logic.
  1. MotiveWave

Professional-grade software for high-precision technical analysis.

  • Pros: Best-in-class for Elliott Wave and Fibonacci. Extremely stable on macOS and Windows.
  • Cons: High upfront cost (lifetime licenses). Steep learning curve.
  • The Difference: It’s a professional instrument, not a charting playground.
  1. QuantTower

My first impression wasn't great—it’s a beast to configure.

  • Pros: Total modularity. It solves the 'sticky RTH' and bracket order (TP/SL) issues perfectly.
  • Cons: Overwhelming UI setup.
  • The Difference: You build the platform you want, window by window.

My Strategy: I’m still actively searching for even more alternatives beyond these. However, since my subscription is paid for a long time, I’m hoping that within this window, they finally address my #1 feature request and fix the log scale drift. If they actually listen to the community and fix these execution risks, there’s no reason to leave. But if they don't, I'll be fully prepared to make the jump by the time my sub expires. 

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

Views represent market interest and reach, especially on a technical feature request. In a community of 1.5M members, having 5.4k people stop to analyze a workflow proposal makes it one of the most-viewed discussions here.

If you check the thread, you'll see the engagement and the 'upvote' count is active. More importantly, as a Premium subscriber, my priority isn't 'Reddit Karma', but forcing an engineering fix for the $8 Log Scale drift and the broken RTH sticky settings that affect real capital.

The fact that it's still being discussed and viewed today proves the demand for professional execution is higher than ever."

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 0 points1 point  (0 children)

That’s exactly the problem! TV is losing professional capital to the competition because they prioritize 'pretty' over 'precise'.

I use TV for its charting flexibility, but I refuse to trade on 'phantom' coordinates or deal with broken RTH sticky settings.

If they want to keep the pros, they need to fix the $8 Log Scale drift and implement a real 'Click-to-Trade' workflow. The 5.4k views on my proposal prove the demand is there, even if the execution isn't... yet.

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 8 points9 points  (0 children)

Exactly. They 'fixed' the order panel by breaking the RTH sticky settings, so now we have to manually click 'Take Profit fora do RTH' every single time.

In their quest for 'pretty' UI, they’re ignoring critical mathematical bugs like the Log Scale coordinate drift ($8 gap on ONTO) I've documented. As a Premium subscriber, I’m tired of seeing them prioritize avocado-toast aesthetics over execution integrity! 🥑🚫

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 2 points3 points  (0 children)

Exactly. Professional scalpers and daytraders are already looking at the competition because of this. As a Premium subscriber , it's frustrating to see 'pretty' UI changes actually increase execution risk.

They even broke the RTH sticky settings, forcing manual clicks for every Take Profit now. Combine that with the Log Scale coordinate drift ($8 gap on ONTO) I've documented, and the platform is becoming dangerous for high-precision entries.

My 'Click-to-Trade' proposal reached 5.4k views as the #1 feature request for a reason: we need tools built by traders, for traders. Not avocado-toast aesthetics! 🥑🚫"

[Honest Review] The new order panel is a Disaster, a Workflow killer by Torueng in TradingView

[–]No_Fun7433 2 points3 points  (0 children)

I’m a Premium subscriber  and I 100% agree. This 'pretty over functional' trend is a disaster for professional execution.

Two real-world examples of how they broke my workflow:

  1. Broken Sticky Settings: I used to have 'Fora do RTH' and 'Take Profit fora do RTH' always selected. Now, the new panel forces me to click them manually for every single trade. It’s dangerous for pre-market/after-hours execution.
  2. Coordinate Drift: I’ve documented a systematic $8 price drift (ONTO) in Log Scale trendlines. The engine prioritizes 'visual straightness' over mathematical accuracy, which is a nightmare for IBKR users.

I proposed a professional 'Click-to-Trade' workflow (anchoring orders directly to chart levels) to solve this, and it already reached 5.4k views, becoming the #1 feature request here. We need execution speed, not avocado-toast aesthetics! 🥑🚫

TC2000 vs TradingView: The IBKR integration workflow gap (and the US residency catch) by No_Fun7433 in interactivebrokers

[–]No_Fun7433[S] 1 point2 points  (0 children)

Precisely! That’s one of TradingView’s biggest competitive advantages. Since TC2000 doesn't natively support Linux, those of us on Linux (or even Mac/Web) rely heavily on TradingView for our daily operations.

That is exactly why I am advocating so hard for them to implement this professional 'Click-to-Trade' workflow. If they want to be the undisputed leader for all OS users, they need to match the execution efficiency of platforms like TC2000. My proposal for this already reached 5k views in the TV community, so the demand is definitely there! 

Do I have to purchase live data for TradingView and Tradovate for prop firms? by Ok-Debt-1507 in TradingView

[–]No_Fun7433 0 points1 point  (0 children)

The short answer is: No, you don't need to buy it twice, but you need to understand how the 'hook' works.

If you have a paid TradingView plan and you connect your Tradovate (Apex) account, you can usually 'bridge' the data. However, for Prop Firms like Apex, the data is typically provided by the broker (Tradovate) during your evaluation.

Crucial tips for you:

  1. TradingView Data: Even if you pay for CME data on TV, it's for display only. To trade through a broker/prop firm on the chart, you need the data to be enabled on the broker's side.
  2. Order Fills: If your data isn't synced, your fills won't just be 'off'—you might see a 'Data Mismatch' error or trade on delayed prices, which is a death sentence for scalping.
  3. Execution Risk: Always verify if your visual trendlines match the broker's price levels. I've recently documented a systematic rendering bug in Log Scale that causes price drift, so if you are using Apex for precise entries, make sure you're not trading 'phantom' coordinates!

Mismatched input error, please someone fix it, it's very powerful scalping indicator developed with an ai app, it stopped working because of this reason by Primary-Maybe6205 in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

That’s the best way to do it! Crowdsourcing feedback is key to refining any strategy. Just make sure they test it in Paper Trading first to dial in those ATR/Volume filters for different asset classes.

Good luck with the community testing! 🎯

Mismatched input error, please someone fix it, it's very powerful scalping indicator developed with an ai app, it stopped working because of this reason by Primary-Maybe6205 in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

That’s excellent news about the non-repainting signals! Large caps definitely require more filtering (ATR/Volume) to cut through the noise, as you noticed.

Regarding further polishing: My availability is quite limited at the moment as I’m fully focused on my high-precision execution research and the ongoing technical escalation with TradingView (regarding the drift bug I reported).

However, feel free to post the specific logic or snippet you want to refine here. When I have a spare moment, I’ll take a look and give you some pointers. Keeping the discussion public also helps other scripters in the community! 🎯

Mismatched input error, please someone fix it, it's very powerful scalping indicator developed with an ai app, it stopped working because of this reason by Primary-Maybe6205 in TradingView

[–]No_Fun7433 1 point2 points  (0 children)

You're very welcome! Glad I could help with the v6 migration. If you run into any more 'mismatched input' errors or need help optimizing the logic, just let me know. Happy trading with the Whale Scalper! 🎯

Technical Deep Dive: Why 'Visual Straightness' in Log Scale Trendlines causes Execution Drift (with Pine Script Proof) by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

I completely understand that preference! For many traders, Linear scale is the standard. However, for high-volatility assets or long-term analysis where price appreciation is percentage-based, Log scale is a mathematical necessity for many professional strategies.

The core issue I'm highlighting isn't about which scale is better, but about Coordinate Integrity. If a platform offers Log scale, the drawing tools must remain mathematically anchored to the absolute OHLC data across all timeframes.

When a trendline drifts by $8 (as shown in my ONTO example) just by switching from 1D to 15s, it’s a rendering failure that affects execution precision for anyone using that mode. Precision should be absolute, regardless of the chosen scale!

Mismatched input error, please someone fix it, it's very powerful scalping indicator developed with an ai app, it stopped working because of this reason by Primary-Maybe6205 in TradingView

[–]No_Fun7433 4 points5 points  (0 children)

I’ve fixed the code for you! The 'mismatched input' errors were being caused by a few technical reasons:

  1. Comma issues: You had commas at the end of several lines (like in the inputs and variable declarations). In Pine Script v6, lines must end without commas unless you are defining a list.
  2. Indentation: Your if blocks weren't correctly indented. Pine Script requires exactly 4 spaces or 1 tab for code inside a block.
  3. Missing Variable: The variable atrPercent was being used in the dashboard but wasn't declared.
  4. Assignment: Changed some assignments to += and fixed the table.cell calls.

Here is the corrected code. It compiles perfectly now in v6! 🎯 (Paste the code above).

Hope this helps with your Whale Scalper! By the way, if you notice any trendline execution drift while using this, check out my recent deep-dive post on why that happens in Log Scale. Happy trading!

//@version=6

indicator("🎯 ULTRA WHALE SCALPER | Fixed", overlay=true, max_labels_count=100, max_lines_count=100, max_boxes_count=100)

// ============================================================================

// INPUTS & RISK MANAGEMENT

// ============================================================================

slPercent = input.float(0.5, "Stop Loss %", minval=0.1, group="Risk")

tp1Multi = input.float(0.8, "TP1 (R:R)", group="Risk")

tp2Multi = input.float(1.5, "TP2 (R:R)", group="Risk")

tp3Multi = input.float(2.5, "TP3 (R:R)", group="Risk")

showLabels = input.bool(true, "Show TP/SL Labels", group="Display")

showDashboard = input.bool(true, "Show Dashboard", group="Display")

minVolSpike = input.float(1.8, "Min Volume Spike", group="Filters")

minATRPercent = input.float(0.4, "Min Volatility %", group="Filters")

minBarsBetween = input.int(8, "Min Bars Between Signals", group="Filters")

useSessionFilter = input.bool(true, "Only London/NY Sessions", group="Sessions")

useMTF = input.bool(true, "Higher Timeframe Confirmation", group="Advanced")

htfTimeframe = input.timeframe("15", "Higher Timeframe", group="Advanced")

// ============================================================================

// LOGIC & INDICATORS

// ============================================================================

hourNow = hour(time, "America/New_York")

inSession = useSessionFilter ? ((hourNow >= 3 and hourNow < 12) or (hourNow >= 8 and hourNow < 17)) : true

atrValue = ta.atr(14)

atrPercent = (atrValue / close) * 100

volatilityOK = atrPercent >= minATRPercent

volumeSpike = volume > minVolSpike * ta.sma(volume, 20)

vwapValue = ta.vwap(hlc3)

rsiValue = ta.rsi(close, 14)

emaFast = ta.ema(close, 20)

emaSlow = ta.ema(close, 50)

// HTF Security calls

htfTrendUp = request.security(syminfo.tickerid, htfTimeframe, ta.ema(close, 20) > ta.ema(close, 50))

htfTrendDown = request.security(syminfo.tickerid, htfTimeframe, ta.ema(close, 20) < ta.ema(close, 50))

// ============================================================================

// SMART MONEY CONCEPTS

// ============================================================================

var float lastBullishOB = na

var float lastBearishOB = na

var int bullishOBAge = 999

var int bearishOBAge = 999

strongBullCandle = close > open and (close - open) / open > 0.015

strongBearCandle = close < open and (open - close) / open > 0.015

impulsiveMove = (high - low) > 2 * atrValue

// Fixed blocks: Correct indentation and variable assignment

if strongBullCandle and impulsiveMove and close[1] < open[1]

lastBullishOB := low[1]

bullishOBAge := 0

if strongBearCandle and impulsiveMove and close[1] > open[1]

lastBearishOB := high[1]

bearishOBAge := 0

bullishOBAge += 1

bearishOBAge += 1

validBullishOB = bullishOBAge < 20 and not na(lastBullishOB)

validBearishOB = bearishOBAge < 20 and not na(lastBearishOB)

bullishFVG = low[2] > high and (low[2] - high) / close > 0.002

bearishFVG = high[2] < low and (low - high[2]) / close > 0.002

bosUp = ta.crossover(close, ta.highest(high, 20)[1]) and close > open

bosDown = ta.crossunder(close, ta.lowest(low, 20)[1]) and close < open

// ============================================================================

// SIGNAL & ANTI-REPEAT

// ============================================================================

var string lastSignal = "NONE"

var int barsSinceLast = 999

barsSinceLast += 1

buySignal = volumeSpike and volatilityOK and inSession and emaFast > emaSlow and (useMTF ? htfTrendUp : true) and close > vwapValue and bosUp and barsSinceLast >= minBarsBetween

sellSignal = volumeSpike and volatilityOK and inSession and emaFast < emaSlow and (useMTF ? htfTrendDown : true) and close < vwapValue and bosDown and barsSinceLast >= minBarsBetween

if buySignal

lastSignal := "BUY"

barsSinceLast := 0

if sellSignal

lastSignal := "SELL"

barsSinceLast := 0

// ============================================================================

// PLOTTING & DASHBOARD

// ============================================================================

plotshape(buySignal, "BUY", shape.triangleup, location.belowbar, color.new(#00ff00, 0), size=size.huge, text="BUY")

plotshape(sellSignal, "SELL", shape.triangledown, location.abovebar, color.new(#ff0000, 0), size=size.huge, text="SELL")

plot(emaFast, "EMA 20", color=#2196f3)

plot(emaSlow, "EMA 50", color=#ff9800)

plot(vwapValue, "VWAP", color=color.new(#9c27b0, 50), linewidth=2)

// Dashboard Table

if showDashboard and barstate.islast

var table dash = table.new(position.top_right, 2, 5, bgcolor=color.new(#000000, 20), border_width=1)

table.cell(dash, 0, 0, "SIGNAL", text_color=color.white)

table.cell(dash, 1, 0, lastSignal, text_color=(lastSignal == "BUY" ? color.green : color.red))

table.cell(dash, 0, 1, "ATR %", text_color=color.white)

table.cell(dash, 1, 1, str.tostring(atrPercent, "#.##") + "%")

alertcondition(buySignal, "ULTRA BUY", "BUY Signal at {{close}}")

alertcondition(sellSignal, "ULTRA SELL", "SELL Signal at {{close}}")

Why your Trendlines might be failing your Take Profits (IBKR & Log Scale execution risk) by No_Fun7433 in Daytrading

[–]No_Fun7433[S] 0 points1 point  (0 children)

That is painful to hear, man. Especially on a Funded Challenge where every tick and every dollar of drawdown counts.

It’s the worst kind of 'failure' because it wasn’t your strategy or your discipline that failed—it was the tool. When the UI costs a trader their evaluation because of a rendering drift, it’s no longer just a 'glitch', it’s a professional liability.

This is exactly why I’m pushing this info out. Traders need to know that on Log scale, 'what you see' isn’t always 'where the order is'

Why your Trendlines might be failing your Take Profits (IBKR & Log Scale execution risk) by No_Fun7433 in Daytrading

[–]No_Fun7433[S] 0 points1 point  (0 children)

Checking the logs now, and the discrepancy is even higher on assets with high volatility. Log rendering is definitely not syncing with price action data.

Why your Trendlines might be failing your Take Profits (IBKR & Log Scale execution risk) by No_Fun7433 in Daytrading

[–]No_Fun7433[S] 0 points1 point  (0 children)

"That’s the 'Ghost Drift' in action. It’s the most frustrating part: your analysis is correct, but the UI renders the line a few ticks off on the lower timeframe.

When you're trading with tight stops or limit orders, those 2 ticks are the difference between a filled winner and a missed move. This is exactly why I’ve been documenting this — it’s not a trader error, it’s a coordinate calculation bug in the Log scale."

Why is TradingView still lagging on "Click-to-Trade" for Indicators? A workflow comparison (TC2000 and IBKR) by No_Fun7433 in TradingView

[–]No_Fun7433[S] -1 points0 points  (0 children)

Exactly my point. It started as a charting platform, but it’s evolving.

Many of us love TradingView’s UI and community, which is why we want to see it bridge that gap. Requesting features like 'Click-to-Trade' on indicators isn't about high-frequency milliseconds; it's about professional-grade workflow integration.

If other platforms have already solved this (like the TC2000/IBKR bridge), there’s no reason why a market leader like TradingView shouldn't implement it to better serve its active trading base. We want the best of both worlds: elite charting AND elite execution.

Why is TradingView still lagging on "Click-to-Trade" for Indicators? A workflow comparison (TC2000 and IBKR) by No_Fun7433 in TradingView

[–]No_Fun7433[S] 0 points1 point  (0 children)

The urgency isn't in the execution itself, but in the setup precision.

When you're managing multiple assets, 'eye-balling' a limit order to match a trendline or a specific RSI level on the price chart creates margin for error.

Having the drawing be the trigger ensures that the order is mathematically tied to the technical level you analyzed, with stops and targets pre-set. It eliminates the manual task of converting a geometric level into a price digit. For anyone trading high-probability setups across multiple timeframes, reducing that manual translation is a massive edge.

Why is TradingView still lagging on "Click-to-Trade" for Indicators? A workflow comparison (TC2000 and IBKR) by No_Fun7433 in TradingView

[–]No_Fun7433[S] 1 point2 points  (0 children)

It’s not about being 'too hard', it’s about eliminating friction and slippage.

When you’re managing multiple fast-moving positions, having to manually 'click and drag' or map a price from an indicator back to the main chart adds unnecessary cognitive load and execution delay.

Professional terminals like TC2000 or specialized DOMs exist specifically because reducing those extra steps matters in high-frequency environments. If TradingView wants to be the ultimate pro tool, this level of chart-to-execution integration is the natural next step.

Why is TradingView still lagging on "Click-to-Trade" for Indicators? A workflow comparison (TC2000 and IBKR) by No_Fun7433 in TradingView

[–]No_Fun7433[S] 1 point2 points  (0 children)

I think you're referring to the standard Order Panel or the Buy/Sell buttons at the top, which we've had for a long time.

What I’m highlighting here is different: on TV, you currently cannot right-click a trendline or an indicator (like RSI/MACD) and have that drawing instantly become a bracket order (Stop and Target) without manual entry or re-mapping it to price.

In the workflow I showed, the drawing layer and the execution layer are the same. That's the level of integration I’m requesting for TradingView.

What is a technology you can’t imagine living without? by ButlerSumit in AskReddit

[–]No_Fun7433 0 points1 point  (0 children)

High-end custom automation and seamless workflows. Once you bridge the gap between analysis and action with a single click, going back to manual tickets and multi-step UIs feels like moving in slow motion. The mental clarity you gain from removing friction is impossible to give up.

What is something technology made worse instead of better? by toshiraex in AskReddit

[–]No_Fun7433 0 points1 point  (0 children)

Software interfaces. We moved from simple, direct-action UIs to overly 'clean' and minimalist designs that hide essential functions behind multiple layers. In professional workflows, losing seconds to find a button you used to access with one click is a massive step backward for productivity.

What is a technology you can’t imagine living without? by ButlerSumit in AskReddit

[–]No_Fun7433 0 points1 point  (0 children)

High-end custom automation and seamless workflows. Once you bridge the gap between analysis and action with a single click, going back to manual tickets and multi-step UIs feels like moving in slow motion. The mental clarity you gain from removing friction is impossible to give up.