Support Board
Date/Time: Tue, 21 Jan 2025 00:47:54 +0000
Post From: ACSIL Triggered trailstop
| [2018-07-13 17:45:31] |
| |
|
These will be added to version 1782: double s_SCNewOrder::AttachedOrderStop1_TriggeredTrailStopTriggerPriceOffset; double s_SCNewOrder::AttachedOrderStop1_TriggeredTrailStopTrailPriceOffset; double s_SCNewOrder::AttachedOrderStop2_TriggeredTrailStopTriggerPriceOffset; double s_SCNewOrder::AttachedOrderStop2_TriggeredTrailStopTrailPriceOffset; double s_SCNewOrder::AttachedOrderStop3_TriggeredTrailStopTriggerPriceOffset; double s_SCNewOrder::AttachedOrderStop3_TriggeredTrailStopTrailPriceOffset; double s_SCNewOrder::AttachedOrderStop4_TriggeredTrailStopTriggerPriceOffset; double s_SCNewOrder::AttachedOrderStop4_TriggeredTrailStopTrailPriceOffset; double s_SCNewOrder::AttachedOrderStop5_TriggeredTrailStopTriggerPriceOffset; double s_SCNewOrder::AttachedOrderStop5_TriggeredTrailStopTrailPriceOffset; In the case of a triggered trail stop order, when the above variables are not set, the original variables will be used instead. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-07-13 17:46:29
|