Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 29 Apr 2024 13:28:22 +0000
Post From: Using Visual Studio C++ to create Custom Studies
| [2021-12-19 12:47:35] |
| Bet_More_Tim - Posts: 21 |
|
Hello, I wanted to ask some questions for clarity based on what User310645 posted about their process I've attached a picture here where I've written notes next to their code, as well as how I assume it's to be used in a final acsil cpp file. So I think most of it is clear, however on 2. I'm not entirely sure what exactly is being done here, and also then relating to the potential usage in an acsil file of that line. the "Study(&sc) {}" is this what goes in the acsil cpp file after SCSFExport ? What confuses me further is it seems another pointer is being passed into the "SetReferences()" function, at which point it seems like there are two pointer references going on? Another thing I wonder is if the subgraphs can be set from the study class file the same way the user inputs are set, and then assign a value to subgraph as needed referencing the variable we named it in the study class, or would it be more proper to set the subgraph values from within the acsil cpp file 'nice and cleanly also' As far as doing calculations with data, I'm assuming that the idea is to pass the sc.Array of the data you want as an argument to one of your study class functions... and this ties into the previous question as well, since would it be more proper to set subgraphs from within the class function itself, or would it be more proper to return a value from the class function and just set the subgraph value to that function call. I'm assuming we would not want to bring actual data out of sierra to "keep" longer than needed, which is my reasoning for a preference being to pass the sc.Array as an argument rather than having separate variables set to inherit those values... but then I have the question, does c++ automatically clear any memory that was used during the calculation of a function, or is there still a need to clear memory in some way. I guess then the idea is to compile your class file as a .dll and drop it in acs_source folder, and afterwards compile your acsil cpp file.... or since the idea is working in visual studio building solutions, with our "including add dir" and dest. folder set, we just "build solution" all at once, and both .dll (study class file & acsil implementation of study) will get built and dropped where we want. Thanks |
 Making_Sense_of_cpp.jpg / V - Attached On 2021-12-19 11:50:23 UTC - Size: 781.89 KB - 423 views |