Noob alert. Introducing myself.
-
Dear all,
This is my first message and I would like to share my doubts with all of you. I recently discovered this site and let me say I find simply fabulous!
I didn't know a place like this could exist on the whole web. I'm a trader for 6 years now and I want to begin to create my own EAs (always trading manually so far).According to the main page "No programmimg skills are required" to use fxdreema. This is what I call a dream come true for a guy like me who has wasted too much money on mql programmers. Well, I read all support and faq info and...I have no idea how to begin!
What has to be put on the Init tab? And in the Deinit one? Why more than 80% of things are punt on the "tick" one and less than 5% in each of all the others?Please, no offense but what do you exactly mean by "No programmimg skills are required"? I just want to know if I missed something important.
Thank you in advance.
Ingmar
-
The whole text is "No programming skills required, only logic thinking". You are probably right about the "programming skills" part or the "skills" part. What I mean is that you don't need to know MQL4 functions and specifics... most of the time. You don't need to actually code, to sit and write code in MetaEditor. In some extend, you really don't need to have programming skills, because you can only connect few blocks and with this you have fully functional EA.
Well, it's much better if you have programming skills or at least the ability to connect the blocks in the best possible way. Many people put blocks here and there, they create a total mess that I'm not sure that even they understand. Other people can create projects with good structure. To keep a good structure, to use less blocks as possible, to reuse blocks, to describe blocks and groups of blocks - these are all programming skills and in the same they are not.
Those "Events" like Init, Deinint and Tick, they come from MQL4. In MQL4 they are functions, for example OnTick(). But this is the technical part...
Why everything is under the Tick event... Because the price changes only when you get a new tick. The whole idea is to do something when the price changes - to buy low and sell high. If the price is at the same level all day long, there is no trading. So, "on Tick" is where the price changes. Again, if there is no price change, you don't want to do nothing. You want the price to move up or down in order to do something.
"on Tick" is also the time component of the program. If you don't do something on every tick, then you have a Script. MetaQuotes call Scripts those programs who do their job once and immediately quit. You can only have program that reacts to certain events if that program is always "listening" for them. The "listening" part is this "on Tick" event, the fact that the blocks under "on Tick" run on every tick.
-
What to put in "on Init"? Nothing or whatever you want. Whatever you put there, will run once when the EA is put to work, before the first tick that it will receive. Do you want to do something at this initiation or not? In "on Init" you can for example check something and use the "Terminate" block to stop the EA before it even start. Or if you want to create some objects on the chart, let's say some button, you just want to do that once and "on Init" is the right place. You can of course do in in "on Tick", but there is no good reason for that.
"on Deinit" runs once when the EA is removed, when it stops working. The same applies here - do you want to do something at that time or not? Normally this is the place for clearing - to delete objects for examples.
-
Thank you very much for your answer. I will try to create my own firs EA soon. As I foresee I will need much help in this beginning, can I post my EAs here to be reviewed by other posters? Or is there a specific place to do that?
-
I can see your projects at any time. But you can make a shared copy and post it here as well, at least it will stay unchanged and then you can continue working on the same project. There are few people who answer to other people sometimes, but still not very often
