
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
When you open the editor, I don't understand why you don't immediately "spread" the panel around the edges of the graph, why do they overlap each other? This is of course a small thing in the global flow, but it's something that catches the eye.
The video showed that Peter's ALL is built with global variables.
There is only one alert handling function for the whole program and only the value comes to it.
This single function checks for changes in all available controls in the global array. And the spoilage of this function will grow as the number of elements on the form increases.
Peter says that you won't have to dig into his code: well, that's exactly the mess you'll have to dig into very seriously. This could be easily avoided if on each case Peter generated default event method passing type, name and value of the control. Then the whole thing would be easily handled in the body of the main EA.
Ok. But to rewrite something, we must have a clear idea of organization.
If you have any ideas, please write them. I think the base classes are :
coordinates
styles on all of the events
and a base class of the object itself.
We are talking about the base classes. To be honest, I'm not very good at graphics... But I can program something, but because I've never dealt with graphics, I may miss the structure (organization of the structure) at the first attempt.
Flaw. Initially, the window is not editable. When the first element is transferred to it, it can be stretched. The auxiliary markup is switched on and the element property values are sent to the properties window, where they can be edited.
Reread my post, I didn't write about an editable window.
Reread my post, I wasn't talking about an editable window.
Because when you first open it, all the windows are positioned in the centre. Rule.
We're talking about "editor" windows! What rule are you talking about? Open any editor and it has all windows glued to the sides of the editor, even in the same meta-editor...
We're talking about "editor" windows! What rule are you talking about? Open any editor and it has all windows glued to the sides of the editor, even in the same meta-editor...
Where is the published code?
Regarding getting and setting values of controls, you need to add simplified functions like this: SetElementValue(element name, value) and GetElementValue(element name).
The same for the properties: SetElementProperty (element name, property, value) and GetElementProperty (element name, property).
The latter functions can be used universally because the "VALUE" property can be passed to get or set a value.
Where is the published code?
As for getting and setting values of controls, you need to add simplified functions like SetElementValue(element name, value) and GetElementValue(element name).
The same for the properties: SetElementProperty (element name, property, value) and GetElementProperty (element name, property).
The latter functions can be used universally since the "VALUE" property can be passed to get or set a value.
There is an important information block missing in the connection file.
Here it is:
It answers the questions about getting element values and other properties.
I'll include it in the api-file. And I'll add examples.
Where is the published code?
1. Regarding getting and setting values of controls, you need to add simplified functions like this: SetElementValue(element name, value) and GetElementValue(element name).
The same for properties: SetElementProperty (element name, property, value) and GetElementProperty (element name, property).
The latter functions can be used universally since the "VALUE" property can be passed to get or set a value.
Partially implemented. The programmatic interaction with the elements can be extended. I will think about it.
Partially implemented. It is possible to extend the software interaction with the elements. I'll think about it.
Strange... you code in your native language, but you write help in English, and then you make invectives against English-speaking clever people.... It's weird...