Posts made by fxDreema

Yes, look at the Trailing Start option... this is basically the level beyond which the trailing stop is working, below that level it the same as you don't have trailing stop at all. And with this, maybe the break even is not needed.

Well, CSV is not just a simple text or value, this is table with values and will be array with values in MQL. How many people can handle that

Until I make block to read files I will suggest to use those global variables that are available for MetaTrader. Not the global variables for the file, but those that can be seen when clicking F3 in MetaTrader. There is a block to set these and they can be read as well: http://prntscr.com/4knlk3 Only numeric values
So, these are stored for 4 weeks somewhere in files. Useful if you want to send some values from one EA to another, or in your case - to keep some values.

Or something like this: https://fxdreema.com/shared/hAdvsbOac
This is the result: http://prntscr.com/4kgw6p

I used two variables, AllowBuy and AllowSell. They can have values 0 or 1. They are both set to 1 in block 2, and then depending on the last closed trade - one of them is set to 0.
Then, before buying/selling these are checked.

This is not correct: http://prntscr.com/4kgpfz
Group mode is a string parameter with undocumented values, I will not recommend to use variables for this parameter and most of the drop-down (with multiple options) parameters.

Otherwise I think you are doing it good. With "For each Closed Trade" you can load the last closed trade and do something with it. Note that when this block loads a trade, only pink blocks can be used to work with that particular trade. Other type of blocks can be used in the loop as well, but they work for themselves. For example, block 19 does not load the last buy trade for block 20, block 20 still works with the trade loaded in block 14.
Again, I will not recommend to use non-pink blocks under "For each...." block, but when needed - no problem.

So, if your Buy was closed on loss, you don't want to open new Buy when the current price is higher than the open price of the losable closed Buy. But you will probably be ok with opening a new sell. Then, can we say that you want to just invert the next trade on loss? If the last losable trade was Buy - wait for Sell condition?

Well, if everything is ok the indicator should appear on the chart automatically. Then the buffers matter

You are talking about this? https://play.google.com/store/apps/deta ... der4&hl=en
I never tried it, but I can see that it has "History" tab with some trades logged, such thing must be available in every trading platform.

If you want to log only certain EA... even the PC version of MetaTrader does not do that, it writes all messages in a single file.

Otherwise SendEmail() and SendNotification() functions can send text. I think you want to create report file and send it as a text message. There are no blocks in fxDreema to create such a report, you are the first one to ask for something like this

http://docs.mql4.com/indicators/icustom

Your indicator file must be named TraderDream.mq4 and it has 10 numeric input parameters (most probably "int" type). Most of them defaults to 0. Better look at them in MetaTrader, there you will see their actual names and data types. Like it is here:

https://fxdreema.com/docpics/indicator_inputs_alligator.png

In fxDreema custom indicators can be defined manually. Look here for more info: https://fxdreema.com/documentation/proj ... indicators

Sometimes I'm with my friends and we are doing something whole day

What remains the same after restarting the EA (and MT itself) is the list of trades with all their parameters, objects and their parameters (if the same chart is used), candles and bars of course, and that type of global variables that can be accessed with F3 in MT4 (these are variables written in some file, so they remain on the disk).

Everything else is temporary in the EA, for example "once per trade/order", other "once per..." blocks, flags, Variables, counters... basically blocks are storing their information in RAM only. For some thing I'm considering using external files to store runtime information, but I don't know when will that happen. And sometimes I think that this is a good idea, other times I thing the opposite

So you don't understand nothing

It's ok for me , maybe some visual problem, but I think it will work even that way.

Fixed for the web version. You can always add another weekday filter for the opposite days as well

Is this the local version? If it is, it's probably some bug I am not aware of, this error message should be seen on the web version only. If you can give mo that EA + the indicator... I don't know what is the problem, but I can inspect it if I get it on my PC

Haha, yes. I started to make this block back then and I have something, but no one else asked, so...
Meanwhile I wanted to create some other website so I started to create my own PHP framework... long story... and these days I started to rewrite fxDreema again

Well, I obviously forgot to reset BuySL and SellSL variables in block 7 https://fxdreema.com/shared/uWdRqpJhb

Well, this really depends, there are different variants that can be made. The question is how do you define that value of 5000 and then how do you want to change it. When the EA is closed, all of it's variables are gone. When you trade, the equity changes. There are things you should decide. And then... I think you can work with those variables

What I can suggest is to look at those variables when you click F3 on MT - as a way to store variables and then manually change them while the EA is running.

I guess you are using "Indicator tester" block. Try with Candle ID bigger than 0, some indicators give information on the previous candles, like Fractals.

Several... these variables that start with "inp_" comes from the checkboxes in blocks, these in the right side of each parameter. I don't recommend these. And I there is something buggy with them and they appear in the code even if visually they are disabled. I'm not very sure about that, but I started to rewrite the whole fxDreema, so I will probably fix those problems meanwhile.

Use these for fast optimizing and then uncheck them, this is what I recommend. For true inputs better use Constants.

Try Fractals with Candle ID = 2 at least

By the way this is how to check indicators: https://fxdreema.com/demo/mt4-indicator-tester

If you define some Constant in fxDreema, it will appear as a single thing in the inputs and can be used in all blocks. And yes, it will not be "ENUM_TIMEFRAMES"