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
I'm not the most persistent person, that's my weakness )
I've already answered the question of what the article is about. But I'm ready to clarify again.
The indicators that are given in the article are given as an example. They perform only one task - they show how to connect the file to be included and what happens after that. I was getting the same screenshots as yours while writing the article. This situation occurs with CHART_EVENT events and, of course, it is not allowed in a working indicator. Here it can't be an error, as I am quite sure. In the training indicators, the event handler is made, but without special frills, primitive. It is not necessary and I did not take into account that these indicators will have to move intensively.
How to work with the code is in the article, you have not read it carefully. Two generated arrays should be fed to the input, I wrote about it. And I give a part of the code that shows how such arrays could be correctly created. Again, the article clearly says that less attention is paid to this particular part (creating arrays). Why? Because the main role is given to the include file. It is kind of a "constant" value. But the second part, where the problems with CHART_EVENT and so on should be solved, is a "variable" value. This part has to be changed every time. Today you need a glass, tomorrow a diagram, the day after tomorrow something else. That's why this part is given a secondary role, the developer will make this part of the code for himself. He will have his own event handlers and methods of creating arrays. And then you just need to add the file to be included. This is the scheme of work described in the article.
And the library file itself cannot be unchangeable either. And it can be edited, added, inherited from classes, etc. I'll tell you more, even if the developer throws out all my code and takes only the scheme "array preparation - manager - diagram", I will be quite satisfied. Although now, after your comments, this is unlikely to happen.
You emphasise what I decided not to dwell on in detail. I thought about it for quite a long time, made that decision and now I continue to stick to it, not out of stubbornness, but because I believe it is the right one. That is why I do not consider what you consider a mistake to be a mistake. That's the situation, unfortunately. It's not about my stubbornness.
I have tested the algorithm itself in combat conditions and it works. I have similar indicators from other sites, other developers, and they show extremely close results to mine. The rounding is different and the scale is different, but that is not the point. Should I have mentioned it in the article? No, probably not.
The correct example you are talking about is a "combat" indicator based on this code. I am working on such an indicator and on the scheme I described. It will be later, but I will definitely post here when it is ready.
О! I didn't answer the very first question. The article is about a library file, basically a piece of code.
Alexey, I can hardly answer your questions more thoughtfully and carefully ) I really hope that it turned out clear, understandable and honest.
If you had clearly stated what the article was for from the very beginning, probably my questions about indicators would not have been asked. And the title, to be honest, is misleading (at least it misled me). Thank you for your detailed reply.
Hello.
My husband has used your work to work in Ninjatrader. Is that possible? Does it violate your copyright?
Thank you.
Hello.
My husband has used your work to work in Ninjatrader. Is that possible? Does it violate your copyright?
Thank you.
No, it doesn't. Let him use it as he sees fit. Good luck to him.)
I will insert my five cents ))
About a year ago I wrote a class for collecting real-time volume clusters CBaseVolume, and several indicators based on it, everything is counted in real time, there is no load, graphics is implemented via CCanvas of standard library:
iDelta M1
iVolumeProfile H1
iVolumeProfile D1 + iDelta M1:
iVolumeProfile M1 filtering volumes by the minimum specified:
also on the basis of this class several robots have already been written, here is the last of them Hidden Profit (HiPr v1.04 ( FORTS )):
ps. this is not an advertisement for sale as everything is implemented only for internal use, with mutual interest I can share it for free, all questions in ls.
Interesting ) I understand correctly that each chart is a separate Canvas?
I used to do it that way, but then I realised everything on a single canvas except for the button and drop-down checkboxes to choose what to display on the chart.
I also made a glass on a separate canvas, but it is there just as a legacy from HFT, there are levels that duplicate the signal from there )) and it is more convenient to select volumes for the algorithm.
Yeah, I can see that))
A lot of work and debugging probably took more than one day )))) And it looks impressive. No doubt it would be interesting to see the implementation. I may well have to do something similar on canvas too.