Support Board
Date/Time: Tue, 04 Nov 2025 08:17:38 +0000
Post From: ACSIL version management in relation to user input evolution
| [2018-06-28 15:36:18] |
| wwwingman - Posts: 185 |
|
Hi I am setting this as a programmers discussion, and hope to have some ideas. The problem I have is that the research tools I build tend to evolve often, and upgrading the chartbooks that use those studies can becomes very time consuming. The evolution of computation is not a problem. It is the evolution of the user input. For ex, on V1 I have 10 integer inputs, but on V2 I end up with a study id input and one float input. Since the V2 and V1 are different in the user input, I build the V2 with a new name. This allows me to have the 2 versions together on 1 chart, but also prevents me from doing mistakes. The DLL name is something like NameOfDLL<VersionNumber>. So are the studies. This means that when I upgrade my charts I need to delete the old study and add the one from the new DLL. Please remember SC saves the current input data. So if I keep the same name for the DLL and study, the input basically is full of junk. Can you suggest a better approach ? I saw in the code examples that you can add a version in the inputs, but this seems limited to very small input evolution. Please advise.. -- W |