Support Board
Date/Time: Tue, 29 Sep 2026 18:09:39 +0000
Post From: ACSIL: letting a custom study use a left-button drag without scrolling (Pointer/Hand tool)
| [2026-09-29 16:39:50] |
| User719512 - Posts: 491 |
|
Maybe consider this design as an alternative to taking over left-button drag while Pointer/Hand is active. Instead of arming a custom study and dragging stop → entry yourself (which fights chart scroll under Pointer/Hand), lean on Sierra’s built-in Reward/Risk drawing tool for the geometry, then have a small ACSIL study turn that drawing into an order action. Flow 1. User draws a normal Reward/Risk chart drawing (stop / entry / target as usual). 2. User selects that drawing. 3. User right-clicks the chart and chooses a custom Chart Shortcut Menu item added by the study (e.g. “Execute Trade from Risk/Reward”). 4. On sc.MenuEventID, the study calls sc.GetSelectedUserDrawnDrawingFromChart(sc.ChartNumber, ChartDrawing). 5. If ChartDrawing.DrawingType == DRAWING_REWARD_RISK, read the levels from s_UseTool and build/send the trade (or for a POC, just AddMessageToLog them). Reward/Risk field mapping (ACSIL) • BeginValue → Stop • EndValue → Entry • ThirdValue → Target Side can be inferred from entry vs stop (entry above stop → long, below → short). Why this may be simpler for order entry • No need to suppress chart scrolling, switch tools to Chart Values, or subclass sc.ChartWindowHandle. • Uses documented APIs: AddACSChartShortcutMenuItem / RemoveACSChartShortcutMenuItem, MenuEventID, and GetSelectedUserDrawnDrawingFromChart. • The user still gets interactive stop/entry/target placement with Sierra’s own drawing tool (adjust handles, labels, R:R, etc.). • The study only runs the “execute” step when the menu item is chosen. Tradeoffs vs your drag-to-order UX • Not a single left-drag gesture under Pointer/Hand. • Requires an explicit select + right-click menu step. • Relies on Reward/Risk being the selected user drawing when the menu item is clicked. If the goal is “define stop/entry/target visually, then fire a sized order,” this path avoids the unsupported window-subclass workaround. If the goal is specifically “armed Control Bar button + left-drag while Pointer stays selected,” then you still need an answer to your original scroll/tool questions — this is just a different product shape that sidesteps that problem. |