Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 02 May 2024 12:30:22 +0000
[Programming Help] - [renamed] Underlying variable locking issue
View Count: 385
| [2020-02-19 02:22:42] |
| User917679 - Posts: 76 |
|
I noticed that when I use a simple command to close when price crosses a level, there appears to be a difference between using ID0.SG4@3, and ID0.SG(2or3)@3; In other words, using the high or low in an active bar to trigger the close at a crossing, and using the last price in an active bar to trigger the close at the cross... Why is this? |
| [2020-02-19 02:41:42] |
| User917679 - Posts: 76 |
|
To clarify a little further, the high/low live price closes as expected, but the "last" live price seems to not necessarily do this...
|
| [2020-02-19 16:33:31] |
| User917679 - Posts: 76 |
|
Actually upon closer inspection, there seems to be an underlying variable locking problem at the open... I'm essentially having trouble using the "buy on first signal, ignore multiple signals" and having a "lock state of a one time condition" mesh well together; If I lock, the ignore multiple signal setup "unravels" and goes multiple again.. Suggestions? EDIT: I've simply made some indicator adjustments that approximate what I was trying to do without necessitating the use of the lock function; I think I'll just go this route, but it would've been interesting to get it to work with how I had it(!) Date Time Of Last Edit: 2020-02-20 02:40:24
|
To post a message in this thread, you need to log in with your Sierra Chart account: