u/Accurate-Mirror-143

Ternary expressions involving UDTs (User Defined Types) do not appear to work reliably in Pine Script, even when both branches clearly use the same UDT.

Example:

UDT_result = bool1 ? UDT_A : UDT_B

with: type(UDT_A) == type(UDT_B)

I would like to understand why this currently does not work (or does not always work), since at first glance it seems that checking whether both branches use the same UDT type should theoretically be straightforward.

Please add pane- and layout-specific context support for input.*() defaults in Pine Script to programmatically enable automatic selection of different indicator configurations within a layout.

Currently, Pine Script already provides several display- and chart-related environment variables such as: chart.left_visible_bar_time, chart.right_visible_bar_time, timeframe.period.

These variables demonstrate that Pine supports limited local chart/viewport context without violating a sandbox or privacy model.

A very useful extension would be pane- and chart-related context support for input.*() defaults.

A typical use case is the simultaneous use of multiple instances of the same indicator within one layout, where each instance fulfills a different functional or visual role (a similar concept as in-app purchases). For example:

left layout column → “Original” engine

middle layout column → “Developmental” engine

right layout column → “Difference” engine

Currently, such multi-instance workflows must be configured entirely manually through redundant inputs.

One possible approach could be:

mode =

input.string(

default = ["Portfolio", "Candidates", "Diagnostics"],

title = "Mode")

Possible semantics:

default

→ pane-related default values within a chart,

→ chart- and layout-related default values between multiple charts of a layout.

A dedicated optional context parameter (e.g. context = input.context_chart or =input.context_pane) may be preferable, as it cleanly separates context selection from the constant default tuple itself (this concept can also be employed for desktop-tab-specific default selection).

The key advantage of this approach is that all default values would remain fully constant. The Pine engine would merely select the appropriate constant element automatically depending on the current chart or pane.

This would keep the entire system: fully backward compatible, deterministic, compile-time constant.

At the same time, complex multi-chart and multi-pane workflows would become significantly simpler, while greatly improving the reusability of modular indicators.

Additionally, the behavior can remain consistent with "overlay" and "force_overlay" particularly regarding assignment to the main pane (pane 0) versus the logical instance position within the chart.

Please add a “Default” / “Reset to Default” entry to the input field context menu. This would significantly improve usability during parameter experimentation, since individual values could be restored selectively without manually re-entering them and without resetting all input fields. Ideally, hovering over this menu entry should also display the corresponding default value, allowing users to quickly look it up if needed.

https://preview.redd.it/weapz8qtxf2h1.png?width=353&format=png&auto=webp&s=172ec734425dcf4f6918dfc05ba41987373071df

Please engage with German brokers that support the standard automatic withholding of German capital gains tax (“Abgeltungssteuer”) in order to establish the prerequisites for combining TradingView-based automated trading with broker integrations that support automatic German tax withholding.

For many German users, the lack of automatic tax withholding is likely the single biggest obstacle to using Pine Script automation together with such broker integrations, since users would otherwise need to manually calculate, declare, and pay taxes on all stock-related capital gains themselves.

It occasionally happens that after modifying a script following a runtime error, and after the indicator has run error-free again, changing settings of other loaded instances of the same indicator, reopening the editor, and clicking the curly-braces icon on the lowest instance of the indicator in the chart, its script is not loaded into the editor.

As far as I remember, what appears instead is a warning about unsaved changes (not specifying which changes are meant) and an “Add to Chart” button instead of the faded “Update” icon. , which seems surprising and illogical to the user in this situation, because under the normal workflow saving is normally enforced before execution, which is already somewhat cumbersome in itself. Only after confirming the save and rejecting the save of a new script name does the script finally appear, As I said, this is based on my recollection.

I would therefore suggest performing a code review to verify whether the implementation truly guarantees that clicking on any of the curly-braces icons UNCONDITIONALLY loads the script of the corresponding indicator into the editor. Based on my observations, this is definitely not always the case, even though I do not know the exact minimum conditions required to reliably reproduce this surprising and illogical behavior.

Even if it were the case that I had forgotten to click the update icon, pressing the curly-brace button should still not unsolicitedly trigger the offering of “Add to Chart” and script renaming.

Now, it happened again:

https://preview.redd.it/2fvc5bvuf12h1.png?width=560&format=png&auto=webp&s=78204152ba7b64fc8a77a4b7ed28b5afc82ae3a6

Please add native Windows 11 Snap Layout support to the TradingView Desktop app (hover on maximize button / Win+Z). This currently appears not to work and would greatly improve workflows, especially when traveling with only a single monitor available.

In the right toolbar, the upper icons open panels to the left, while in split-view the lower icons open panels to the right (except for the Help Center). This effectively represents two separate radio-button groups.

A very practical detail is that clicking an already active upper icon closes its panel again. Unfortunately, this behavior is still missing in the lower group in split-view.

The existing X-shaped close button inside the respective panel should certainly remain. Nevertheless, it would create less cognitive friction if the lower radio buttons behaved in split-view consistently as well, i.e., if clicking an already active icon also closed its corresponding panel.

Please add an “Add another instance to chart” item to the Pine Editor script menu. This would greatly simplify adding the same indicator multiple times with different settings directly from the editor.

When developing larger Pine indicators or libraries, intermediate states are often non-executable (including non-compilable) and therefore not intended to become part of the official script version history.

It would therefore be very helpful to support a separate storage or repository layer dedicated to such non-executable states, for quickly saving temporary working states using either autosaves or manual saves, without affecting the main version history of the script.

Please ensure that every watchlist alert stop is always recorded in the Alert Log together with the exact reason. Currently, watchlist alerts sometimes appear to stop silently or without sufficiently clear diagnostics.

In Overlay View, the Pine Editor width should be reducible to the same extent as in Split View, so more chart space can be used without having to close and later reopen the editor window.

Please add native GitHub integration for Pine Script projects, including repository synchronization, direct import/export, version control support, and optional one-click deployment from GitHub to TradingView. This would greatly improve Pine Script development workflows, and backup reliability.

Please preserve the Pine Editor split-view layout when restoring the desktop window from maximized to windowed mode.

Currently, the right-side Pine Editor panel disappears and must be reopened manually each time.

Of course, the editor width may be reduced automatically when restoring the window — even to a minimal width if necessary — but the Pine Editor panel itself should remain available and directly enlargeable by dragging its left border.

Please introduce a separate undo/redo history exclusively for the currently open Pine Script. Script changes should be undoable/redoable step-by-step independently from the general chart/layout history and be applied immediately.

https://preview.redd.it/9xjkqecrcu0h1.png?width=418&format=png&auto=webp&s=a47063132cc8f060ff819dea0a9cc17a2ab90138

Please provide a context menu item “Substitute by latest indicator version” that allows the indicator to be directly replaced with its most recent version. Currently, updating requires manually removing and re-adding the indicator, which is highly cumbersome and confusing from a user perspective.

https://preview.redd.it/cslgkd8rh3yg1.jpg?width=565&format=pjpg&auto=webp&s=a33f6ff1c7ccfd4c80a8f3bcb8581c6173508364

Please make the full error message directly copyable from the context menu (right-click), without requiring any part of the message to be selected first.

https://preview.redd.it/ufehiskg73yg1.jpg?width=421&format=pjpg&auto=webp&s=87e594bcb0f6c5a91596b3401aa52e84c3c27825