Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Nowhere without you - 6. - page 951
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
How can I make an indicator subwindow invisible, preferably from the code? (if at all possible)
I wanted Alert to show the normalized point value. But it returns 0.00001000, it should be normalized after NormalizeDouble function?
I wanted Alert to show the normalized point value. But it returns 0.00001000, it should be normalized after NormalizeDouble function?
DoubleToStr() will help
Thank you, that helps! But what if I need to do mathematical operations with Point? When you output it by Alert, it outputs a 16 hex digit 1e-005.0. After normalization, it's 0.00001000. To display it, we need to convert it into a string form, but you can't perform arithmetic operations with a string. How can I cut off the extra 3 zeros at the end and still be able to perform mathematical operations?
And why are you bothered by extra zeros?
Storing and displaying numbers are slightly different things
Thank you, that helps! But what if I need to do mathematical operations with Point? When it is output by Alert, it outputs a 16-digit number 1e-005.0. After normalization it is 0.00001000. To display it, we need to convert it into a string form, but you can't perform arithmetic operations with a string. How can we make it possible to cut off 3 extra zeros at the end, and still be able to perform mathematical operations?
After N-bars this line is no longer needed, but the indicator continues to consume memory.
I have a question - if I just null the buffer values for the bars exceeding {0-N} -
will it free up memory?
There is an indicator buffer in the code which is used to draw a line on the chart.
When N bars pass, this line is no longer needed, but the indicator continues to consume memory.
I have a question - if I just zero out the buffer values for bars outside {0-N} -
will it lead to memory freeing?
No
to initially allocate some range for them (e.g. 0 to 2000) and not exceed it?
Do I understand correctly, the only way to avoid memory overrun by indicator buffers is
to initially allocate a certain range for them (e.g. from 0 to 2000) and not exceed it?