Enum HeatmapLeaseMisuseReason

Why a HeatmapLeaseMisuseException was thrown. Lets callers distinguish misuse classes without parsing the message text.

Added in ATAS 8.0.15.

public enum HeatmapLeaseMisuseReason

Extension Methods: Extensions.ConvertToMyTrade<T>(T, Portfolio, Security, Action<MyTrade, T>)

Fields

LeaseAlreadyHeld = 0: BeginUpdate() was called while a previous lease was still in flight. The platform serialises every callback on a single per-instance task, so this almost always means the indicator passed the lease across an await point or to a background task.
WrongDescriptor = 1: A HeatmapIndicatorVisualHandle minted from one descriptor was presented to a state built from a different descriptor.
UnknownVisual = 2: A handle's visual id is not present in the state — typically a stale handle that survived a descriptor rebuild.
WrongVisual = 3: A HeatmapIndicatorSeriesHandle<TValue> was presented to the wrong visual lease.
UnknownSeries = 4: A series handle's id is not present on the visual — typically a stale handle from a previous descriptor revision.
MissingValueProjection = 5: A series handle was minted via the decimal fast-path (Series(string, HeatmapIndicatorSeriesRole, HeatmapIndicatorValueKind, HeatmapIndicatorVisualStyle?, string?, string?)) but the runtime TValue is not decimal. Use the generic Series<TValue>(..., valueProjection) overload to bind a projection at descriptor build time.