Support Board
Date/Time: Wed, 27 Nov 2024 08:38:58 +0000
sc.FlagFullRecalculate Question
View Count: 1502
| [2014-08-08 23:39:03] |
| Kiwi - Posts: 375 |
|
I found a message referring to this acsil function and understood that setting it to 1 would cause a recalculation. I assumed that it would force recalculation of every study on a chart. So I tried it on a true live (customChart) study thinking that it would force the chart to recalculate from the beginning thus filling in the bars missing after I did a delete and refresh data - UpdateStartIndex would drop to 0. But it doesnt seem to do that for this study. I don't think it did it for the others. Can you refer me to the documentation that says what sc.FlagFullRecalculate is intended to do please. No hurry; it just seemed a nice way to tidy up some software? |
| [2014-08-09 00:24:01] |
| |
|
You need to check your own code. When using this flag, there is most definitely a recalculation of all studies on the chart starting at index 0.
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 |
| [2014-08-09 05:18:34] |
| Kiwi - Posts: 375 |
|
Thanks, It turns out that I was setting it too frequently and this prevents it working. When I set it on a 10 second loop it worked fine. |
| [2014-08-09 07:30:40] |
| Kiwi - Posts: 375 |
|
Note: This is NOT an issue for me now as my goal was just a "nice to have." I just put this observation down in case you face a related problem in future. There was another issue. I had an SC instance with a 5000ms chart update interval. With a 15 second dely on recalc commands that chart never recalced. When dropped to 1000ms it worked, even with a 5 second delay on command releases. So something is getting confused by either recieving the command when its in the wrong state (and it can no longer accept them) or ...? Also, I've discovered that it will work on a chart with true live and a couple of other studies. But with 5 or 6 it stops working even though it is definitely fired. So its sensitive to something else and I can't figure out what it is. Date Time Of Last Edit: 2014-08-09 08:14:05
|
| [2014-08-09 21:27:36] |
| |
|
We discovered a problem where when the chart contains more than one study, that the recalculate may not occur depending upon which study is setting this flag and the order of the studies. If it is set by one study, and a second study is calculated which is later in the calculation order, then the flag would get cleared. This is fixed in 1173. 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 |
| [2014-08-10 00:28:13] |
| Kiwi - Posts: 375 |
|
Just confirming that 1173 removes all the quirkiness. It works perfectly across multiple charts with an interesting combination of overlays and different precedence levels. An excellent new feature. |
To post a message in this thread, you need to log in with your Sierra Chart account: