My approach. The core is the engine. - page 129

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
Work with the version of the engine you attached as a demonstration.
It's pretty straightforward. If your approach works as I think it does, then I don't see any problems with either a dynamic table or updating position values via a timer. Peter, why did you make a mess from the start?)
Vasiliy, the main thing is not to rush to conclusions. Neither for you nor for me)).
I'll put in my five cents. I don't have time for it at the moment. But there is such an idea to implement a similar panel at home. So I think not just do a cross to close the position (although it is necessary), but also make a mark, specify the lot and do this wholesale closing. That will give more flexible work with positions, as well as their partial closing.
I can do that.
Peter, make a for loop in the timer, which would go through the open orders and send changes in the orders list to your table. Also, make the order profit in your table also change dynamically.
Vasily, please paste this code into the test EA file (the tick and timer functions instead of the old ones)
And also, you have to replace line 68 and line 114 in the External Connection file.
A little bit mixed up there. Instead ofOrderOpenTime() putOrderOpenPrice().
It should work fine. Check it.
Eh, not the canonical thing to do - separate data(model) from views and use the observer pattern to subscribe specific views to model changes or specific model fields.
But that would require the user of such a library, to think object-oriented and shove their EA data into the proposed object structure (yes, yes, you need to learn the methods of that library/framework to build an interface). And many people don't know a thing about OOP.
But Peter says you don't have to learn anything! Just go ahead and stick your global variables in the ready-made spool of generated handlers and the interface will work. Yes it's a godsend guys! It's not "make planks for a shelf, connect them according to the instructions and arrange books", but "draw your shelf and arrange your books on it". Code Less Do More ((c)/JQuery if you are)
Clearly, there are problems with product positioning. And what if it is? Hey, programmer! Do you want to make some money? You may sell what looks good! Take a hundred or so Expert Advisors without interface and sell them with interface. hahaha ))
Well, there's a disadvantage of interface file, in which the handlers of controls "stick out" - it's static. I'll have to rack my brains and create a new handler type that would act as a template and accept user/program data via input parameters.
Eh, not to do the canon...
It's OK, Rehtag will do Konowam. )))
Eh, not the canonical thing to do - separate data(model) from views and use the observer pattern to subscribe specific views to model changes or specific model fields.
But that would require the user of such a library, to think object-oriented and shove their EA data into the proposed object structure (yes, yes, you need to learn the methods of that library/framework to build the interface). And many people don't know a thing about OOP.
But Peter says you don't have to learn anything! Just go ahead and stick your global variables in the ready-made spool of generated handlers and the interface will work. Yes it's a godsend guys! It's not "make planks for a shelf, connect them according to the instructions and arrange books", but "draw your shelf and arrange your books on it". Code Less Do More ((c)/JQuery if you are)
Clearly, there are problems with product positioning. And what if it is? Hey, programmer! Do you want to make some money? You may sell what looks good! Take a hundred or so Expert Advisors without interface and sell them with interface. hahaha ))
Well, there's a disadvantage of interface file, in which the handlers of controls "stick out" - it's static. I'll have to rack my brains and create a new handler type that would act as a template and accept user/program data via input parameters.
At first I thought it's another batch of negativity, but then I read it better and it turned out not. Just emotions.
This constructor is intended for people who are really keen on algorithmic trading. It makes sense for them not to waste their time studying graph libraries but just to create such a code:
And get a window with a din table.
In the interface file the user will get this code:
And it will determine what to do and how to do it on button click events.
The next dynamic table will be even more interesting. The cells will have input fields, pop-up lists, checkboxes, buttons, radio buttons, progress bars, and input fields with +/- buttons.
The tricky part is the dynamism of such a table. After all, accessing elements and getting their values is not tied to specific parameters, but depends on the row layout.