Support Board
Date/Time: Thu, 21 Nov 2024 23:19:38 +0000
Post From: Version 2151 Available: Foundation For Millisecond/Microsecond Timestamping
| [2020-08-15 14:55:19] |
| binaryduke - Posts: 369 |
|
Triggered by post #20, we have been testing as regards our post #8. Our studies create their inputs and subgraphs from core routines that are called during SetDefaults based upon the requirements of each study. This is to avoid duplication of code as we have many common Inputs and Subgraphs used by various studies. We have noticed that we are getting exception errors during the assignment of an SCString (that we create) to a subgraph, e.g. SCString ExampleName; SCString ExampleSuffix; int VariableNumber; VariableNumber = 3; ExampleSuffix = " Example"; ExampleName.Format("Subgraph %i %s", VariableNumber, ExampleSuffix.GetChars()); sc.Subgraph[0].Name = ExampleName; This style causes an exception error. The Call Stack lists: SCString::StringDelete(chart * String) Line 766 there seems to be an issue with m_DefaultString <Error reading characters of string.> SCString::Initialize() Line 280 This style/functionality has been working fine prior to v2149/v2151. Should we await v2152? As an aside, we do NOT use contiguous members of the sc.Subgraph array, e.g. we may use 0,1,2,3,4,58,59. We had an issue with this approach and the sc.Input array that we discussed with you here: Strange behaviour when populating sc.Input array and here: Custom Studies has issue on windows 10 (post #24 relating to changes to the DisplayOrder member) and modified our approach accordingly. While I see that our use of non-contiguous members of the sc.Subgraph array could be causing the problem, the exception errors occur on the first call to our routine i.e. when populating sc.Subgraph[0]. We have also tested using contiguous members of the sc.Subgraph array by inserting code prior that sets the DrawStyle of all available subgraphs so that each member of the sc.Subgraph array is populated. |