I found the problem, it will be fixed in the next build 🙂

Er... sorry. I'm back!

When I make an entry in the text are in block descriptions, this is not saved:

1 - create a "Pass" block
2 - edit title to "testing"
3 - click "Save" and/or "Export to..."
4 - close fxDreema local
5 - open it again

...and the title of the block has returned to "Pass"!

Help!

🙂

Now I'm preparing few new blocks to work with the chart, I guess very soon.
What I can suggest is to check in the source code what is the timeframe that is selected, it should work. The problem is that names are shifted with one step, so H4 is actually H6, H6 is H8 and so on. When the fix comes it will not need any intervention, you can actually see on the project you posted that it now shows H6 🙂

Yes, works fine 🙂

well you're the expert , i have no clue yet when it comes to the differences between MQL4 and 5 , i just started learning MQL4 and do not understand it much unfortunately because the context is different from object oriented languages which i'm an intermediate level, but i'll get there, i hope!

figured it out - I had illegal character "/" in title of file

I will check that, don't update these blocks. But I have some problems with my computer and I don't know when I will fix it, so if you have build 70 - you can use it.

So it's working. I was not able to reproduce this exact error, but I was already found something else and it looks that both problems were connected 🙂

looks good!

I think I fixed this problem, it was about 2 months old.
Now I can see that the properties of "Modify Variables" looks weird and I will go to fix it. If you mean something else, tell me.

I think it is ok now

Is there error otherwise? I fixed some problem yesterday, but who knows, maybe another is introduced?

The idea is that when a global variable is used in block, and that variable is with the same name with some local variable for this block (each block is a function in MQL4), then the local variable is prefixed with this "l0ca1_" thing.
In your case, in the block is used variable named "GridStart", and you probably had Variable with the same name, so to not mix them in the function the one that is local is renamed everywhere in that function.

I tried it now, it is ok for me. Maybe it stopped downloading or something like this. And if you are with IE, I'm not sure it will actually re-download the file. So my suggestion is to try again or with another browser. Otherwise this is WinRar SFX archive and you can also open it with WinRar - there is "fxdreema.exe" and empty "Data" folder there.

I think it's ok now. It was something with the latest Chrome.

Now instead Constants, Input checkboxes are used. No difference at that point 🙂
I think this is better: http://fxdreema.com/shared/zrV0t7UBd
The only points where SL can be modified are BE and TS. If you got "Error: Invalid SL requested" again, put it here. I have made a little update where it will print Ask/Bid price instead open price.

These MM options (% of...) are maybe not useful in every situation. If it is "% of Balance" and the value is 100(%) and Balance is 10000 and the market is EURUSD when 1 lot is 100000, then the lot size will be 0.1.

I think this indicator is loaded, but can't be read or something like that. Is it working otherwise, if you use it manually? Or within another EA somewhere from internet? And after these error messages, will it eventually start to work or they have no end?
How about input parameters, are they ok? - the same parameters count and order, the same datatypes or at least compatible datatypes?

Things are not "now and then", they are always "now". And you can expect that as I can see, because you are using "Once per tick" block, which is actually not needed.
So, when you have conditions like this - one after another - if the first one is not true, the next one will not be checked at all. Let's take "5 MA x> 50 MA" for example - this condition can be true (the block can pass) multiple times in one specific candle, but not all the time after that condition. "5 MA > 200 MA" can, it is always true and the block always passes (if executed) when MA5 is above MA200.

Play with this to see different crossover situations and what is going on: http://fxdreema.com/shared/tpuyHHxdb

Can you show me more details? Maybe the name of the block, or part from the MQL4 code that contains this error + some more rows from above and below?

can you look at these blocks
they seem to be back to front

OK ...the Indicator problem is gone ...
I uninstal and reinstal Crome in my main PC.
Now FXDreema works perfectly .. i think so 🙂