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
OK.
the CFrame is clear.
---
I noticed that you went down the path where gui blocks are each represented by their own bitmap.an important point for those reading this and who have already started to think about it:
should only work on one bitmap, with all gui elements rendered on it. Including the z-order.
In this case, there will be more possibilities for rendering. (shadows, gradients, etc.)
And control is simplified (we will not go to the level of MT objects)
In this case, the shadow of a window may be implemented as an alpha-channel bitmap and thus remove the computational load of calculating this shadow.
All GUI elements of a single window are drawn on its bitmap considering Z order and nesting (I don't know how to call nesting of GUI objects correctly)
Monitor mouse events through CHARTEVENT_MOUSE_MOVE, I did it in my projects, no lags found.
Using other events without loss of mouse input quality was not possible.
It only remains for me to implement the events that the GUI engine will call according to the description in the text file.
IMHO, each individual application window (dialog) should have its own bitmap and object on the chart (do not even consider the case where multiple EAs or indicators will "abuse" one bitmap resource).
In this case, the shadow of a window may be implemented as an alpha-channel bitmap and thus remove the computational load of calculating this shadow.
All GUI elements of a single window are drawn on its bitmap considering Z order and nesting (I do not know how to call nesting of GUI objects)
this is correct.
I would add that not just "every dialog", but specifically one bitmap per expert/indicator. More is possible, but this is at the coder's discretion.
I think that when you have a working dialog on the bitmap, then adding modal windows on the same bitmap or another dialog on the same bitmap is a technical matter and is not important right now.
First of all, we make an abstract model without specifics, e.g. which windows are located where, etc..
Then you will be able to cover all the different features and behaviours
Greetings coders.
There's an interesting task to do something really useful, and I think crowdsourcing would be a good option.
First, the results will be available to everyone in the early stages. Second, we will make something new using MQL. And maybe we will even ask the MT developers for new goodies.
----
So here is the first and basic task.
1. We need to make a class of button (let's say GButton, prefixed with G not to confuse with existing ones).
- So far the button is simple with text (no extra pictures)
- the button is drawn on a certain area of the canvas
- the button has a click event.
---
In time we will make the codes on the bitbucket.
The ideal GUI is designed in a separate application and imported as XML for example. It's not a good idea to describe the location of buttons and dialog forms in an EA.
Layout:
Implementation of events:
In general, it would be ideal to have a GUI that is designed in a separate application and imported as XML for example. It's not a good idea to write the layout of buttons and dialog forms in the Expert Advisor.
there )
you come to our first task, which we will do after creating the elements.
In general, it would be ideal to have a GUI that is designed in a separate application and imported as XML for example. It's not a good idea to write button layouts and dialog forms in an EA.
In that case, you should start by writing a fast and good XML parser. It's quite a handy thing to have around the house. I'm using one version of CodeBase myself, but it's really slow on some tasks, especially in new builds. I've already got all these patches and crutches in it. In general, write a good parser comrades! Make it easy for everyone.
Maybe you know how to make a working and fully drawn slider? In general terms at least... I'd like to learn the general concept.
Maybe you know how to make a fully working and fully drawn slider? In general terms at least... I'd like to learn the general concept.
look into CCanvas class. all rendering primitives are available.
secondly, you can load bmp for your empties and shuffle them a la BitBlt onto the canvas.