My approach. The core is the engine. - page 65
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
Good. But, -.
1. no programmatic change of element status is implemented.
2. No DLL code has been posted.
You haven't posted the code of your samovar core engine. Why then complain that you weren't given it too?
You have not laid out the code of your samovarskogo engine nuclear. Why are you complaining that you were not given it too?
Oh, like secret technology. All right.))
Well, what's the point? I told you that everyone will puzzle out how to do it.
And I have all clear and understandable...
It's about the states of the elements: pressed/pressed/locked.
Does it make much difference if it's pressed/repressed or colour and text? Pressed/repressed is a bool parameter. Do you think passing a bool parameter has any special difficulties and differences from passing a string and int? The parameter transfer from EA to dll and how the controls react to it is shown. Frantically looking for something to get to the bottom of?
The function that returns the value in the usual way is not shown. But still we show return of parameters by reference. So it's enough.
Does it make much difference if it is pressed/repressed or colour and text? Pressed/repressed is a bool parameter. Do you think that passing the bool parameter has any special difficulties and differences from passing the string and int? The parameter passing from EA to dll and controllers' reaction to it is shown. Are you frantically looking for something to get to?
No. Just when the number of parameters of elements to be changed increases, the complexity of the dll increases.
Imagine there are dozens of elements... Or even hundreds... And the number of element parameters that need to be changed are...
In short, you need to know C# and write dlls on a steep level.
What mass-marketing is there...
And you can't sell it on Market...
No. It's just that when the number of item parameters to be changed increases, the complexity of the DLL increases.
Imagine there are dozens of elements... Or even hundreds... And the number of element parameters that need to be changed are...
In short, you need to know C# and write dlls on a steep level.
What mass-marketing is there...
And you can't sell it on Market...
In short: for three hundred thousand MAs, do you need three hundred thousand functions? No. You only need one. And it's the same here - different sets of parameters are passed to one method to get a different set of results.
No. It's just that when the number of item parameters to be changed increases, the complexity of the DLL increases.
Imagine there are dozens of elements... Or even hundreds... And the number of element parameters that need to be changed are...
In short, you need to know C# and write dlls on a steep level.
What mass-marketing is there...
And you can't sell it in the Market...
To pass an event from dll to an Expert Advisor, you have to add a call to a method of a special class to the event handler - one line.
To control the controls, you need one property and one function (or two functions, a line in each). The functions controlling several parameters can be written. It is possible to pass arrays. All common programming tools are available, so the result depends on how you know how to use them.
Реter Konow:
...
It's not a mass market...
You can't sell it on the Market...
You're still going to sell your hoover on the market?
But, the problem is somewhat solved. I admit it.
Not somehow, but normally solved.
To make a long story short: do you need three hundred thousand functions for three hundred thousand MAKS? No. You only need one. And it's the same here - different sets of parameters are passed to one method to get a different set of results.
Well done. Congratulations. ))