Discussion of article "How to create a graphical panel of any complexity level" - page 6
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
New article How to create a graphical panel of any complexity level has been published:
Author: Vladimir Karputov
Thank you very much for share. Excellent!
I missed just one thing in your example. You should help how to include data information as text and numbers.
For example:
Stop Loss Value:50.50
Take Profit Value: 250.00
Moving Average (200): 110.5.
Do you know any article to teach how to do this kind of thing?
Thank you very much for share. Excellent!
I missed just one thing in your example. You should help how to include data information as text and numbers.
For example:
Stop Loss Value:50.50
Take Profit Value: 250.00
Moving Average (200): 110.5.
Do you know any article to teach how to do this kind of thing?
Check out the standard panel examples in the MetaEditor.
Can you help me with this question.
I added the panel shift function setShift() to your "AppWindowTwoButtonsClass" file. Now if we move the chart border to the right and it comes close to the panel, the panel will start moving to the left along with the chart border.
The call of this function is highlighted in yellow.
The question is: is there any way to call this function through this pseudocode?
so that the call was made from the inheritor class and not from the global OnChartEvent() function.
I tried several defines: ON_NO_ID_EVENT(event,handler), ON_OTHER_EVENTS(handler). But I don't understand how they work.
I am attaching a file with the additional function setShift().
Very useful, thanks for posting.
If YOU really do not see the difference, you urgently need to throw away the old terminal. The old terminal affects you badly. Unfortunately, the old terminal taught you to write very dangerous code - you are used to writing code WITHOUT CHECKS to return errors.
If YOU really do not see the difference, you urgently need to throw away the old terminal. The old terminal affects you badly. Unfortunately, the old terminal taught you to write very dangerous code - you are used to writing code WITHOUT CHECKS to return errors.
It wasn't a dig at your post by any means, it was more of a question as to why this is done so I learn for it - my programming knowledge is very limited.
It wasn't a dig at your post by any means, it was more of a question as to why this is done so I learn for it - my programming knowledge is very limited.
I have already explained: you cannot write code that does not check for error returns.
I have already explained: you cannot write code that does not check for error returns.
Hi Vladimir
this is a well written piece, good job
regards Paul
Hi Vladimir
this is a well written piece, good job
regards Paul
Thanks