Support Board
Date/Time: Sat, 21 Dec 2024 16:07:52 +0000
My Custom Studies work on 1090 SC Version but do NOT work on version 1217
View Count: 997
| [2014-12-12 16:50:27] |
| CMG - Posts: 179 |
|
My Custom Studies work on 1090 SC Version but do NOT work with the 1217 version, any ideas on how to solve this problem? Thanks in advance for your help |
| [2014-12-12 17:29:19] |
| |
|
You need to debug this yourself. It is completely impossible for us to even begin to have any understanding of the problem or make a suggestion unless we were to have the source code for the study and do step-by-step debugging and understand what the study does. However, this is not within the scope of our support. Refer to this page about debugging https://www.sierrachart.com/index.php?page=doc/doc_DebuggingDLLs.html Generally a study should work fine from one version to the next, but over long periods of time, there could be a minor change which could affect a study in some cases. Usually a recompile is all that is necessary though. 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: 2014-12-12 17:30:12
|
| [2014-12-12 18:03:48] |
| CMG - Posts: 179 |
|
Maybe and it is just a humble suggestion you should look into the new version and analyse what has changed and document it. Can you imagine having to write all my code again of a study I made 2 years ago that has been working fine all along? |
| [2014-12-14 22:57:48] |
| CMG - Posts: 179 |
|
The problem was a parenthesis in a formula. I added a parenthesis that solved the problem. The old version study keep working without that parenthesis. !! |
| [2014-12-16 04:24:45] |
| |
|
Can you imagine having to write all my code again of a study I made 2 years ago that has been working fine all along? Yes we can imagine that but it is not that extensive and these things should be expected over long periods of time. You do not have to rewrite the code, you have to review it and identify what the problem is. Sometimes code requires maintenance and review.We can see that you identified the problem, but before that, how do we even know what the problem is and even if it relates to a change we made? We have absolutely no idea whatsoever. It is impossible for us to even comment on that in the slightest. And there are no changes in ACSIL involving parentheses. The parsing of parentheses involves the C++ compiler which we do not develop. Any significant changes to ACSIL are documented on the What is New page. Sometimes there are changes which might not be documented and are insignificant and harmless. For example there might be something like the renaming of a variable which would be detected when you recompile, but this does not affect existing compiled code. 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: 2014-12-16 06:20:15
|
To post a message in this thread, you need to log in with your Sierra Chart account: