
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
Who knows why it doesn't work...
works in C++
What makes you think the scheme wasn't drawn up, was there a prerequisite for that???works in C++
What makes you think there's no schema, was there a prerequisite for that?Where is it? I haven't seen it in three pages.
I was thinking to make a basis for using which would be reduced to minimal code style New_Window<<<Window_Upper.Size; New_Window<<Window_Upper.Position; New_Window.Size<<0.5 (the size automatically becomes half of the above); ...
And this class already takes into account the relationship from the position of the small cross to the higher window (base).
Looks like it's not gonna go smoothly... it happens.I was thinking to make a basis for using which would be reduced to minimal code style New_Window<<<Window_Upper.Size; New_Window<<Window_Upper.Position; New_Window.Size<<0.5 (size automatically becomes half of the above); .
And this class already takes into account the relationship from the position of the small cross to the higher window.
...
Well I have already described many times the "flaws" that from my point of view I see in the standard library and in Anatoly's library.
Both libraries have, in my opinion, one significant disadvantage: interface is built on discrete chart objects,that is, the more controls in the interface, the more isolated objects in the chart itself. On the one hand it's not a problem in itself, but on the other hand it's a problem with drag and drop dialogs, as not a single "form with elements" object is dragged, but many different elements. And this consumes additional resources.
Anatoly's library is very chic, but it is complex in its composition and difficult to integrate into the main program. And the standard library is limited in the controls themselves, although the original architecture is very good in my opinion.
In fact, the best solution would be what Petr Konov tries to do: GUI GUI builder with GUI code generation, but with extended event model, so when integrating with main program, you would not have to dig into huge GUI code (something like MVVM analogue), and of course with objects that users could extend on their own.
Of course, this is a very simplified view on the problem of graphical libraries. It's not about dragging and dropping forms and the lack of kanvas handling, which limits possibilities and functionality of GUI. The bottom line is that MT-objectshave few properties, and library handlers are not sufficiently developed to manage the drawn elements and to support all their diverse capabilities. The complexity of the MT objects and the controlling functionality of the libraries does not reach the minimum level required by the kanvas.
Taking these libraries and rewriting them for kanvas means raising them to a fundamentally new level, which a priori cannot be easy and simple.
ZS. Anatoly started the way to kanvas in his library and was the first to create drawn tables in MKL. However, the method of constructing them is imperfect, due to the fact that cells are semi-independent elements and there are difficulties in addressing each one individually.
I remember what the transition cost Anatoly and how long it took.
It's more or less like this
That's the end of the coordinate class. I don't even know what's next.
I think we should add positioning, though.
Next, in, left, top. cent.....
It goes something like this.
You also forgot this:
It goes something like this.
And that's what's missing:
And this is what's missing:
I wanted to use templates but they don't compile, the simplified example on the previous page
And it's not sure that it will be exactly int and not some enum, and then you don't want to correct the code
And why do we need a bool there?
Ideally, it should be so
And no TD3 (in fact the entire class is written for two values). Why did I call TD also written in the code