
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 do you think? What is there that the standard library can't handle?
Okay, Dimitri. The public here doesn't want to give up. I may not be much of an artist. But I tried to show the possibilities of the designer. They are quite wide. You can create not only quickly, but also beautifully (well, that's for those who are more talented than me in drawing).
I will demonstrate the code of the clock window:
Sure, the code is big. But it is extremely simple.
The main thing is that elements with already set properties (size, colour, gradient) can be simply taken from the code and copied to other windows.
No syntax, no classes, etc... They just took an item, or a group of items, or the whole window and paste it anywhere. In one piece.
Then, change something and you get a new element, element group or window.
...But I tried to show possibilities of constructor...
Here:NEW_WINDOW, W_NAME, "Time limits", W_ICON, "Schedule (16x16)", W_TYPE, SETTINGS, ALWAYS_ON_TOP,
That's what you're trying to portray as an OOP, only in your... in your own way. This is essentially a constructor call: new Qwerty(z,x,c).
Here:NEW_WINDOW, W_NAME, "Time limits", W_ICON, "Schedule (16x16)", W_TYPE, SETTINGS, ALWAYS_ON_TOP,
That's what you're trying to portray as an OOP, only in your... in your own way. It's essentially a constructor call: new Qwerty(z,x,c).
Perhaps. But the order doesn't matter here.
For example:
or .
It makes no difference.
Note that properties can be set for a whole group of the same type at once:
Maybe. But the order is not important here.
For example:
or
It makes no difference.
Note that properties can be set for a whole group of similar elements at once:
If the order is not important, then there are no tooltips. And when you call a function or class constructor with parameters, the compiler makes hints by parameters. And you know, this is a very significant help. So the standard approach is a definite fat plus.
The level of graphics in the standard library is not good, to say the least. The labour involved in creating these windows, for example:
Huge. THAT'S WHY NOTHING SERIOUS IS CREATED.
I doubt that with the standard library you can create such graphics in principle.You're just out of your depth :(
It's very simple and quick. All your windows can be made with the standard library. Really, I won't do it :)
You're just not in the loop :(
It's very simple and quick. All your windows can be done with a standard library. Really, I won't do it :)
Try to make, that at pressing one button one set of control elements will be displayed, and at pressing another one another control element will be displayed. At the same time, you will be able to minimize and maximize the window. It's also assumed that there could be a lot of variants.
It would be interesting to ask Peter how he could solve this problem.
Try to make one set of controls appear when you click on one button, and another set of controls appear when you click on another button. At the same time, the window can be minimized and maximized. It's also assumed that there could be a lot of variants.
It would be interesting to ask Peter how he could solve this task.
There is such a possibility. I can make one element control the phenomenon of another element, or group of elements. Well, and regular tabs work too, of course.
I'll make such an engine today and show it to you.
Try to make one set of controls appear when you click on one button, and another set of controls appear when you click on another button. At the same time, the window can be minimised and maximised.
Is there a problem? I don't have time to investigate the standard library, but I think if hide/show doesn't solve the problem, you could probably swap containers, client areas, or the dialog itself.
Is there a problem? I don't have time to investigate the standard library, but I think if hide/show doesn't solve the problem, you could probably swap containers, client areas, or the dialog itself.
I don't know, I tried it and it didn't work.