So I presume that the Brand object is going to push the new indicator values back to the Data accumulator object.
I hadn't considered that. I would probably Push the results to a different Object, just for debugging logging. Turn it off for speed during Production runs. Just another Custom Setting.
I am not worried about Startup and Initialization times. I consider that to be a Capital Expense. I want to minimise Operating Expenses, CPU load and Time. The only OE I want is the Calculator Objects, and, data Passage and Parsing. Everything else should be a Capital Expense.
Is the Brand object also going to be the one that tests last 15 samples of the three indicators to see is a trigger has occurred,
Do that in another object.
where the split between a 20ms update rate and a 200ms update rate is occuring in your model,
I'm ignoring CPU Timing. The Brand Object is all based on when an object is ready. Since the Main Brand Object is "Ready=True" as soon as all its Children are ready, It will trigger another round of Calculating and data Transfer as often as programmatically possible. I think that as soon as the Brand Object Pushes its Decisions to the Excel Helper Application's CellPrinter UDO, the Brand starts over with the latest BA output.
In Fact, the Excel Helper Application's CellPrinter UDO might be the one to log that data stream. It will be in a different Process.
NOTES TO SELF: All Parent or Container, Objects need Ready=True Event
pReady = Child1.Ready And Child2.Ready And...
Do While Not pReady 'Any good ideas for this?
DoEvents
Loop
'Ouput all data, Main Brand Object only
Application.CellPrinterObj = Me.Data 'Array
pReady = False
'Or, Output Data, then
Do While pReady 'OutputValue Property Gets cumulatively reset pReady to False when read
DoEvents
Loop
Me.Start Over
Local and Global Reset Methods
Method ResetGlobal() Passes ReSetGlobal to all Childs
Method Reset("Child") Passes ResetGlobal To Named Object
Need good ChildCollection Object
Need pPArent Object in each Child
@ All
Given good Child Collections and pParent Objects, can a grandChild and a grandParent use each others Properties?
As simple as GloballyUniquePropertyName = X?
Or something like Me.Parent.Parent.Property = X?
Can a Cell in one instantiation of Excel refer to anything in an different Instantiation of Excel?
How?
Thanks. Off to DuckDuckGo now