BoxInside MT5
FREE
Publicado:
28 maio 2018
Versão atual:
2.8
Não encontrou o robô certo? Encomende um para você
no serviço Freelance.
Ir para o Freelance
no serviço Freelance.
Como comprar um robô de negociação ou indicador?
Execute seu EA na
hospedagem virtual
hospedagem virtual
Teste indicadores/robôs de negociação antes de comprá-los
Quer ganhar dinheiro no Mercado?
Como apresentar um produto para o consumidor final?
Você está perdendo oportunidades de negociação:
- Aplicativos de negociação gratuitos
- 8 000+ sinais para cópia
- Notícias econômicas para análise dos mercados financeiros
Registro
Login
Você concorda com a política do site e com os termos de uso
Se você não tem uma conta, por favor registre-se
I will definitely check it out, no later than the end of this week.
Okay then, thanks.
Ok. I'll check it out myself, and then let you know.
Sure, still waiting mate..
Sure, still waiting mate..
Yeah, I'm sorry, I just forgot.
I'm just busy with a new project, got carried away and forgot.
Today I will check out the problem we discussed above.
Yeah, I'm sorry, I just forgot.
I'm just busy with a new project, got carried away and forgot.
Today I will check out the problem we discussed above.
In fact, I suspect what the problem is, and once long ago (I remember) I already discussed this problem with someone.
The fact is that the indicator uses several buffers of different colors to display dots.
But, when the volume increases at the POC level, or when the colors are re-sorted during the development of the chart history, the dot can change color.
For example, the dot on the candle was green, but then it turned red.
In the green buffer, the dot disappeared and its value turned to zero, but in the red buffer the dot appeared and its value, on the contrary, turned from zero to positive.
To avoid this problem, just need to call the indicator in the mode DrawingMode=Curves, and read the readings from the last buffer, that is, from the purple buffer.
In fact, I suspect what the problem is, and once long ago (I remember) I already discussed this problem with someone.
The fact is that the indicator uses several buffers of different colors to display dots.
But, when the volume increases at the POC level, or when the colors are re-sorted during the development of the chart history, the dot can change color.
For example, the dot on the candle was green, but then it turned red.
In the green buffer, the dot disappeared and its value turned to zero, but in the red buffer the dot appeared and its value, on the contrary, turned from zero to positive.
To avoid this problem, just need to call the indicator in the mode DrawingMode=Curves, and read the readings from the last buffer, that is, from the purple buffer.
Doesn't work... and that's not a solution... would be nice if you post the indicator on the code base section, then I could stop 'bothering' you...
Doesn't work... and that's not a solution... would be nice if you post the indicator on the code base section, then I could stop 'bothering' you...
Hello.
I wrote an indicator that displays the text values of all the buffers of the BoxInside indicator.
This indicator calls values from 100 candles, but displays only the last 10 text values from each buffer.
Displays only 10 values, because there is not enough screen space to display 100 values, but 10 is enough for clarity.
As I wrote above, and as we can now see, there is only one positive value in each column of values, and all other values are zero.
If, during the development of the chart, the value is such that it should change its color, then this value jumps over the text lines above or below, and zero is formed in its former place.
And this is correct, because each buffer displays only its own color.
In other words, on the same candle can be present only one dot of only one color, but two and more dots of different colors cannot be present there at the same time.
However, if we call the indicator with the value Mode=Curve, then we will see that now all the values are not scattered across the buffers, but they are located in one line, but in two buffers.
These two buffers simply duplicate each other, and one of them draws a curve, and the second draws dots on this curve.
This is not just a solution, but it is the only correct solution.
The file is attached.
Hello.
I wrote an indicator that displays the text values of all the buffers of the BoxInside indicator.
This indicator calls values from 100 candles, but displays only the last 10 text values from each buffer.
Displays only 10 values, because there is not enough screen space to display 100 values, but 10 is enough for clarity.
As I wrote above, and as we can now see, there is only one positive value in each column of values, and all other values are zero.
If, during the development of the chart, the value is such that it should change its color, then this value jumps over the text lines above or below, and zero is formed in its former place.
And this is correct, because each buffer displays only its own color.
In other words, on the same candle can be present only one dot of only one color, but two and more dots of different colors cannot be present there at the same time.
However, if we call the indicator with the value Mode=Curve, then we will see that now all the values are not scattered across the buffers, but they are located in one line, but in two buffers.
These two buffers simply duplicate each other, and one of them draws a curve, and the second draws dots on this curve.
This is not just a solution, but it is the only correct solution.
The file is attached.
Thank you for repeating the explanation, but I did understand 100% the first time.
Therefore, I just replicated the same code you sent as EA. Please take a look at the attached files.
From my perspective, seems you're running away from the point of the discussion.
From my perspective, seems you're running away from the point of the discussion.
To be honest, I overlooked that earlier it was about calling the indicator in non-visualization mode.
And now I know exactly what you're trying to tell me.
This is very strange.
What is the difference between a call with visualization and a call without visualization ?
If we call the indicator from the outside, is it called in the visualization mode ?
When calling the indicator, does the terminal create a window for it, even if this window is invisible ?
For some reason, I am sure that when the indicator is called, the terminal does not create any window.
To be honest, I don't understand what's going on there.
I will certainly look at the source code and think about it.
But in fact, there is nothing in the source code that would require launching (calling) in the mode with visualization.
From my perspective, seems you're running away from the point of the discussion.
Still, there, in the source code, there is something that requires running in the mode with visualization.
I will think about how to fix this, and whether it is possible to fix it so as not to harm those users who use the indicator just visually.
Still, there, in the source code, there is something that requires running in the mode with visualization.
I will think about how to fix this, and whether it is possible to fix it so as not to harm those users who use the indicator just visually.
Indeed! That's strange. From what I understand, there is no difference in calling it with or without the visual mode.
I also can't say what is going on, especially because I'm not seeing its code. I think there is something in there for sure.
Regarding harming the other users, maybe you could put the solution (if possible) into conditions like if (MQLInfoInteger(MQL_TESTER) && !MQLInfoInteger(MQL_VISUAL_MODE)) { do this way };
Anyway, you know better than me. Hope you fix it, your indicator is quite useful.
Hello Evgeny.
Any update regarding the bug found?
Hello Evgeny.
Any update regarding the bug found?
Yes, I'll do it.
Wait a bit, I'm just busy with a new project, and I'm very excited.
Better yet ... write me a private message.
Hi Evgeny.
I can't get the value of buffer 0!
Hi Evgeny.
I can't get the value of buffer 0!
Hello.
For information about accessing the indicator buffers, see the comments on this page above.
If you have a similar problem as a Drake user (buffers are normally read in visual mode, but buffers are not read in non-visual mode), and if you need to read buffers in non-visual mode, then let me know.
Hallo Evgeny,
Boxinside MT5 is a very nice and helpfull indicator.
I only need the POC of a candle. So my question is, is it possible to have an indicator only with the POC where I can change the size of the Dots or have small horizontal bars instead of the dots. I would prefere small bars. I trade in M3 and if I zoom out to see a longer time periode, the dots are so big that I see only dots instead of short candles.
I also have the problem that I do not see the POC dots in M1, would be nice to have that. If you can build such an indicator I would definetly pay you for that.
Thanks in advance
Oliver
Hallo Evgeny,
Boxinside MT5 is a very nice and helpfull indicator.
I only need the POC of a candle. So my question is, is it possible to have an indicator only with the POC where I can change the size of the Dots or have small horizontal bars instead of the dots. I would prefere small bars. I trade in M3 and if I zoom out to see a longer time periode, the dots are so big that I see only dots instead of short candles.
I also have the problem that I do not see the POC dots in M1, would be nice to have that. If you can build such an indicator I would definetly pay you for that.
Thanks in advance
Oliver
Hello.
This indicator cannot work on the M1 timeframe, since the minimum unit of information that the indicator uses is M1.
However, in order for the indicator to work on the M1 timeframe, a minimum unit of information is required less than M1.
The display of the VAL and VAH levels can be disabled using the input variables VALcolor and VAHcolor by setting these values as "None".
As for displaying POC levels with smaller circles (or dashes), I will think about this in the next version.
Уважаемый автор, вопрос по работе индикатора, когда выставляешь лимит отображения индикатора по барам, вся информация пропадает!
Можете подсказать в чем дело? Спасибо!
Уважаемый автор, вопрос по работе индикатора, когда выставляешь лимит отображения индикатора по барам, вся информация пропадает!
Можете подсказать в чем дело? Спасибо!
Здравствуйте.
Проверил у себя.
Но у меня не пропадает, а почему-то отрисовка идёт со смещением влево.
Ну то есть, небольшой кусок истории (справа налево) индикатор почему-то игнорирует.
Однако, если настроить масштаб окна графика так, чтобы всё заданное в BarsLimit количество свечей помещалось в окне графика, то индикатор работает нормально.
Либо же, настроить BarsLimit равной нулю, и тогда в качестве самой первой свечи для вычислений и отрисовки (слева направо) индикатор автоматически применяет свечу, лежащую на левом борту окна графика, и индикатор также работает нормально.
Пробуйте пока так, а я попробую разобраться в чём причина данного глюка.