HaasOnline’s purpose is to help more people gain control of their financial freedom as the new age of finance evolves. As a trusted partner to investors and a leading provider of financial technology, our customers look to us for the solutions they need when designing and executing on their most important trading strategies.
local settings = CC_SuperInputSettings('some default value', 'a tool-tip', 'a group!', 2)
local someVar = CC_SuperInput('Input', 'Some Input', settings)
if someVar.FieldChanged then
LogWarning('some setting was changed, recalculate AI...')
local value = someVar.FieldValue -- get value from input field
This topic was modified 2 weeks, 5 days ago by pshai.
The idea was to be able to make scripts more optimized. There could be something you need to calculate based on some inputs you get, but is slowing down your script execution. But if those inputs stay the same (like they probably will for quite some time), it could be better to re-calculate those heavy-values _only_ when you change the values.
Is there a way to check if a CC or calculation in some part of your script is slowing down execution or resources used per command dependency.
To find things SuperInputs would improve, or to avoid in general or any other way avoid sluggish execution?
Maybe there are common bad practices an optimisation check script could detect.
[These are more inspirational than straight questions. I assume something like this doesn’t yet exist. Unless I’m over complicating this and theres a check list or simple way to do this..:)]
Your example makes me curious what might benefit here, can you give an obvious/notorious example? (Interval, VWAP reset loopback those kind of things?)
And SuperInput works in running HaasBots so can maybe help people running 50+ scripts?
This reply was modified 1 day, 9 hours ago by Kobalt.
Unlock your crypto trading potential
Create a free account and enjoy everything we have to offer.