My approach. The core is the engine. - page 133
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
You can't hear me again! And not just me...
Just read it at last:
https://www.mql5.com/ru/docs/basis/types/object_pointers
https://www.mql5.com/ru/docs/basis/types/typedef
I'm reading it. Objects, pointers to objects.
So? What's in it for me? I'm doing fine as it is, if you noticed.
And this approach had a chance. As a result, I ended up with a not very popular graphical library, which is very much inferior to my constructor in terms of capabilities. So why should I go down this path?
and will you apply it? here's an example of dynamic pointers to functions, I was dealing with typedef:
I'd be happy to apply it, if (as in the case of Unions), I see a practical use for it. I repeat: PRACTICAL, not virtual.
OOP, is a virtual thing. It won't help me. I need practical things. Such as pointers to physical memory or unions.
Here I am reading. Objects, pointers to objects.
So? What's in it for me? I'm doing fine as it is, if you noticed.
And this one had a chance. As a result, I ended up with a not very popular graphical library, which is greatly inferior to my constructor's capabilities. So why should I go down that road?
Yeah, very noticeable by the limitations on the number of columns in the table.
I will gladly apply if (as in the case of the Unions) I see a practical benefit. I repeat: PRACTICAL, not virtual.
OOP is a virtual thing. It won't help me. I need practical things. Such as pointers to physical memory or unions.
Maybe you should at least familiarize yourself with the basics first, then give your "super-expert" opinion?
Here I am reading. Objects, pointers to objects.
So? What's in it for me? I'm doing just fine, if you've noticed.
And this approach had a chance. As a result, I ended up with a not very popular graphical library, which is greatly inferior in its capabilities to my constructor. So why should I go down that road?
Haven't noticed yet.
Is that your phrase? :The hardest part is exactly the dynamism of such a table.After all, calling elements and getting their values is not tied to specific parameters, but depends on the magee of the row.
Study this issue. Overcome your protest to comprehend new things!
I assure you that you will enjoy it more than units and resources...
OOP is a virtual thing. It won't help me.
You're hopeless, OOP is not much different from structured programming, you made sure of that when you "took apart the Canvas class".
ZS: I remember Don Quixote and his windmills, you're something similar in your fight against OOP)))
Here's a quote:
And why would I want to do that when I've had an event model organised a long time ago? It works perfectly. Debugged and tested.
It's all a phase that's been passed. This is for those who are "learning the ABCs" of GUI development. For me it's like studying an ABC book again.
Haven't noticed yet.
Is that your phrase? :The hardest part is exactly the dynamism of such a table,because referring to the elements and getting their values is not tied to specific parameters, but depends on the row's magic.
Study this question. Overcome your protestation of comprehending new things!
I assure you that you'll enjoy it more than unions and resources...
Ok. Consider me a sheep in knowledge of OOP. ))
You're hopeless, OOP is not much different from structured programming, you made sure of that when you "took apart the Canvas class".
Remember Don Quixote and his windmills, you are alike in your fight against OOP)))
Quite right. PLO is a wrapper. To some it helps them think and organize their thoughts. Like tram rails help trams run on the streets. I'm in an "off-road" vehicle. )))
All right. Think of me as a sheep in the knowledge of OOP. ))