The future of automated trading - page 22
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
What can you argue with a man who's never eaten anything sweeter than a carrot in his life? How can you tell him what watermelon, melon or orange tastes like? You can't.) If he tries it he will spit from the habit :)))
Do you need the Trading Platform to be similar and do the same thing as, for example, Visual Studio? Now you make me laugh. :)
I tried watermelon and melon. I used to write Win applications at one time, and sometimes even now. Now mostly dlls.
Even a simple full-fledged API terminal would be quite enough for me. Not wildly and ridiculously truncated. This example, with the file functions, is typical.
You want all the functions in the terminal and none of them outside.
Then a bare api, all functions from their dlls/prog.
The hub of the earth in one word (two, to be exact), and to close a deal manually you have to write a separate shell?
In general, the essence of the dispute is not visible, I'm not going to discuss your extremes further.
You do not seem to know what you want.
You want all the functions in the terminal and none of them outside.
Then a bare api, all functions from their dlls/prog.
In one word, the centre of the earth (two, to be exact), and to close a deal manually, you have to write a separate shell?
In general, the essence of the dispute is not visible, I do not intend to discuss your extremes further.
I did not immediately understand what you mean. Now I've got it - don't you know what API of the terminal is?
In general, of course, at this level there is no way to discuss it.
But you should change your username, it is not good to be called Mr. prof for such lack of qualification.
I didn't know what you were talking about at first. Now I guessed - you don't know what the API of the terminal is?
Trade functions and, correspondingly, obtaining coding and other trivialities onlly. Everything else must be written in ASM.
I'll even answer more precisely, with the SHFileOperation() function from shell32.dll.
The kernel has everything you need to do this.
Shell32 is really more of an OS shell...
Not just trading functions. I recommend that you learn a little bit of the basics. For example, file and string functions are also APIs.
If someone mixes in the left functions into the API of the terminal, it is no longer a pure API of the terminal, but a vinaigrette.
The kernel has everything you need to do this.
Shell32 is really more of an OS shell...
It's just easier to implement with this function, and this dll is in all widows from 3.1 (or thereabouts).
So it's not about where to import functions from, it's about the fact that it's possible in MT.
It's just easier to implement it with this function, and this dll is in all widows from 3.1 (or thereabouts).