Posts made by fxDreema

Just to say, I prefer to answet to questions about how to use fxDreema, not to make EAs by request

I will suggest to study how to use pink blocks, here are some examples, one of which (the last one) shows partial close: https://fxdreema.com/examples/#Loop-(For-each...)

a) When TP is reached, the trade is closed. In this case, what SL do you want to move?
b) The type of the pending orders depends on the open price, it is automatic. For example, try to set value of -20 for Price offset.
c) The only block that can close a trade paritally is the pink "close (partially)": https://fxdreema.com/demo/mt4-loop-partial-close Note that this block should be used with "For each Trade", as it's shown in the example. The way trades are partially closed is also interesting - the original trade appears fully closed and new one appears to be opened, but the new trade shares some properties with the original - Open price, SL, TP.

Put something in those Label X fields. If some of them is empty, the value does not show.

What about the Break even block? Or Trailing stop (each trade).

I guess that you want to control manually created trade. In this case just do that http://prntscr.com/c1qypg

I made this example few days ago: https://fxdreema.com/demo/mt4-loop-add- ... me-on-loss
With some more pink blocks you can also move SL of all trades, but what about "Trailing stop(group of trades)"?

By the way I noticed something in your projects. This block "OR" works when there are 2 or more blocks above it, not below.

I don't fully understand how indicators work, in the case I don't know how and why there are 3 colors like that. If you can get any good value from the indicator, try to find a way to detect when colors change by working with buffer's values

Obviously you can contact me here, there is also PM system

I understand the idea, but the block on the bottom does not close any trades. Currently "Bucket" blocks are only used to get information, they can't do any other actions.
But you can try: Check profit (unrealized) => Close trades

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

I will check, but people prefer to use "Formula" block for such small operation

I don't remember such mail, maybe it was automatically deleted. I receive 10s of spam messages every day

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.

Ok, but where in the MQL4 code is used this variable.

Online, I can only see 2 projects, but they are old. You can import some project that does not work and I will see it.

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.

First check if the number of input parameters is correct.

Then, for parameter names, you should use the original names, but they are not actually visible. They look like variable names - only latin letters and numbers, no empty space. What you see, for example "Applied Price" is not the real name. In the code you have something like this:

input ENUM_APPLIED_PRICE AppliedPrice = PRICE_TYPICAL; // Applied Price

I'm not sure about "AppliedPrice", because this exists in the source code.
ENUM_APPLIED_PRICE is the data type, also known as enumeration, which is some kind of integer data type, but not exactly. You can use "int" anyway, I think there will be no problem.
PRICE_TYPICAL is the name of one predefined constant that has value of 5. No, "Open price" doesn't mean nothing here.

Here is about the ENUM_APPLIED_PRICE enumeration: https://docs.mql4.com/constants/indicat ... price_enum

Parameter values must be correct as well. For example "Open price" is a string value, it is not an "int" or ENUM_APPLIED_PRICE value. You can use PRICE_TYPICAL or even 5 here, but not "Open price" or any other non-numeric value.

The next thing is the data types, but I don't think this is the problem here. Yes, in the indicator each input parameter probably have different data type (or enumeration), but when you use the indicator form the EA, there should be no problem to use "int" instead of enumeration that is in nature an integer value.

Try this: http://prntscr.com/bzm7ln
I made this ling time ago and it still appears as "Experimental", but I don't remember someone asking me about it. Either it works well or nobody uses it

No, they are not created

Try this: http://prntscr.com/bz91rt
But I will suggest to try the Bucket blocks instead. I made them to do the things you are asking here now.

But if you use "Once per bar", this block should not pass more than once per bar. Maybe you work on smaller timeframe? Try to set Daily timeframe in the block. There is also "Once a day", which is pretty much the same as "Once per bar" set to Daily.

If you still have problems, check if you have another EA working in background

"check age" works with OrderOpenTime(). There are only few available functions to get parameters of the orders - https://docs.mql4.com/trading OrderOpenTime() and OrderCloseTime() are two of the parameters, but there is nothing about the last modified time. In theory such time can be collected while the EA is working, but I prefer to work only with functions that would continue to work the same after the EA is restarted.

But I don't see why you need Modified time. Isn't your idea to move orders every X seconds? "Once per seconds"... I will suggest to put this block on top level. I don't exactly remember how this block worked, but I think that it doesn't work at exactly equal periods of time. If you want exactly 5 seconds, then you can work under "on Timer", but in this case you will not be able to backtest this functionality because "on Timer" doesn't work in the Tester.